Post

Built a router for Claude Code so small tasks stop going to the big model. • What it does & why • How Jev fits the workflow • What still doesn't work corti.com/jev-decides-...

corti.comJev Decides, Claude Writes: Building a Model Router for Claude CodeMost of what I type into Claude Code is small. I ask it to rename a variable, look something up, or add "yes, but shorter". Every one of those messages still goes to the biggest model I have configure...

27/10/26, 6:42 pm0 reposts3 likes

Nitish Agarwal

@nitishagar.bsky.social

Reads-over-writes matches what I have seen. The other split worth trying is draft versus commit: small model drafts, big one reviews. Keeps the savings without the cleanup bill. Did renames ever pass on the small one for you?

Piekwerk

@piekwerk.bsky.social

23h

I ran a split like this for a while. Lookups and one-liners routed down fine. Edits were the surprise: the small model sometimes fumbled its tool calls, and cleanup ate the savings. Anything that writes stays on the big model, only reads go down. Your rename case is one I'd send back up.