Show HN: Effort Router: Intelligent /effort selection per Claude turn
github.comDynamic effort selection, while possible in some other tools like OpenCode, does not exist in Claude Code.
Having dynamic effort set per conversation turn means:
- Less tokens burned on easy queries (e.g. something low /effort can do goes to xhigh because it's the convo default)
- You avoid mistakes: Prompts requiring high effort (like a refactor or security threat modeling) go to high or xhigh instead of medium to reduce likelihood of mistakes and reduce wasted tokens.
I created this out of a personal need and it's been game-changing. My Claude sessions are way more productive with less back/forth.
Give it a try and feel free to contribute!
Does this not cause you to lose cache because the effort is in the system prompt, so you will burn your usage faster dynamically changing effort in the same conversation?