Portal by Spotify cut my Claude Code token usage by 90%
engineering.atspotify.com
Portal by Spotify cut my Claude Code token usage by 90%
1–10 of 167 posts
Re: Portal by Spotify cut my Claude Code token usage by 90%
#2I've never had an issue with Codex or Claude reading massive files, they're really good at precise greps.
Re: Portal by Spotify cut my Claude Code token usage by 90%
#3Re: Portal by Spotify cut my Claude Code token usage by 90%
#4Re: Portal by Spotify cut my Claude Code token usage by 90%
#5You can also just delegate this to subagents with Claude Code (though you have a more limited choice of models unless you swap the cheaper models via OpenRouter).
I'm OK using a dumb model as a smart grep, but the whole point of using the frontier models is using their intelligence for the hard stuff like coding.
Re: Portal by Spotify cut my Claude Code token usage by 90%
#6Re: Portal by Spotify cut my Claude Code token usage by 90%
#7Re: Portal by Spotify cut my Claude Code token usage by 90%
#8So this is just delegating certain work to dumber models? I certainly wouldn't use Gemini 2.5 Flash (!!?) for code writing as suggested. I've never had an issue with Codex or Claude reading massive files, they're really good at precise greps.
Re: Portal by Spotify cut my Claude Code token usage by 90%
#9Re: Portal by Spotify cut my Claude Code token usage by 90%
#10So this is just delegating certain work to dumber models? I certainly wouldn't use Gemini 2.5 Flash (!!?) for code writing as suggested. I've never had an issue with Codex or Claude reading massive files, they're really good at precise greps.
And why stop at 90%? I have this one weird trick to reduce Claude Code token use by 100%: use a different harness and model!