I stopped hitting Claude's usage limits – things I changed(twitter.com)
twitter.com
I stopped hitting Claude's usage limits – things I changed
https://twitter.com/0x_kaize/status/2038286026284667239
7 comments
in the Claude Code realm I use GSD and it manages all that and keeps token use low. Plus it writes to a file so memory is stored so I can type /clear and the token count resets yet it still can remember where I left off for the next work.
Check it out here:
https://github.com/gsd-build/get-shit-done
https://github.com/gsd-build/get-shit-done
Also use /compact. Slightly easier than copy pasting into new chat. But I forget not everybody uses Claude code
/compact also takes an optional instruction parameter, e.g. exclude the data format discussion.
I tend to just /compact when I reach a good point within the context of a task at hand, then start a new chat when that task is complete. Good documentation, planning and structures tend to help a lot as well.
Points 1, 2 and 3 also guard against the LLM going down the wrong path. Keep that context clean.
I've been using Opencode alongside Claude, trying to utilize Opencode for as much easy/rote functionality as possible so I don't blow through my Claude context, but it is a pain in the rear. I'm sure someone on here has solved this for themselves, and I'd love to hear what people are doing in the "token efficiency" realm.