Hacker News new | ask | show | jobs
by rebolek 42 days ago
> "For the last 15 months or so my hobby has been shouting at Claude"

How can you shout at Claude when it’s

1) foobaring, bamblabooing and fghrtawing all the time without telling you what’s going on

2) when it finally interacts, it’s asking for a permission you told it 30 seconds ago "yes and do not ever ask me again until heat death of the Universe"

3) and after all of that, it just spits out: "you’re out of tokens, give up your liver or wait until next Trump’s war"
2 comments
wolttam 42 days ago
> foobaring, bamblabooing and fghrtawing all the time without telling you what’s going on

Oh man, now I have to plug my tool[0]... it doesn't hide anything, but by default tries to provide a pleasant interface (ctrl+o to toggle details similar to CC, but less janky?)

Disclaimer: It's way simpler than Claude Code or even pi (on purpose)

[0]: https://codeberg.org/mlow/lmcli

link
davidsong 42 days ago
The proper way to work with Claude or Codex is, IMO, to load up the context with a discussion about what you're doing and why. You go back and forth, pushing back on its opinions and shaping the context until the tokens are ready to flow into the right shape. Every angle you miss is an opportunity for them to slop out all over the place, and, until Codex was mature, the longer you ran the task for, the more it'd spread out and lose shape.

Re-shaping the context sometimes involves severe pressures like "wtf is this ugly crap?" or "did I just spot you laying a turd in my codebase again?" and other strong forms of disapproval, mixed with "hmm not sure I like the sound of that"s, to "yea that's much better" to pull it back in the other direction.

The trick is to shape the flow before the tide comes in and you end up like King Canute

link