Here is a gist that tries to patch the system prompt to make Claude behave better https://gist.github.com/roman01la/483d1db15043018096ac3babf5...
I haven’t personally tried it yet. I do certainly battle Claude quite a lot with “no I don’t want quick-n-easy wrong solution just because it’s two lines of code, I want best solution in the long run”.
If the system prompt indeed prefers laziness in 5:1 ratio, that explains a lot.
I will submit /bug in a few next conversations, when it occurs next.
So I think the system prompt just pushes it way too hard to “simple” direction. At least for some people. I was doing a small change in one of my projects today, and I was quite happy with “keep it stupid and hacky” approach there.
And in the other project I am like “NO! WORK A LOT! DO YOUR BEST! BE HAPPY TO WORK HARD!”
So it depends.
https://code.claude.com/docs/en/cli-reference#system-prompt-...
--append-system-prompt
--append-system-prompt-file
--system-prompt
--system-prompt-file
Can this script be made to work without patching the executable?Edit: tried patching with revised strings of equivalent length informed by this gist, now we'll see how it goes!
https://github.com/Piebald-AI/tweakcc
Pushed it to my dotfiles repository:
https://github.com/matheusmoreira/.files/tree/master/~/.twea...
The tweaks can be applied with
npx tweakcc --applytokensSaved = naiveTokens - actualTokens
- naiveTokens = 19.4M — what ix estimates it would have cost to answer your queries without graph intelligence (i.e., dumping full files/directories into context)
- actualTokens = 4.7M — what ix's targeted, graph-aware responses actually used
- tokensSaved = 14.7M — the difference