Live data from Hacker News

Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

systima.ai

51–60 of 433 posts

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#51
post #3

No surprise, I've noticed that "agents", not only CC (I am using Copilot) are trying to be "clever", searching for a lot of data. This is good for LLM providers as this eats a lot of tokens.

OpenAI, to their credit, seems to be focusing pretty heavily on token efficiency in GPT 5.5 and beyond.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#52
post #13

I am forced to use cloude code at work but a good solution is to just use --system-prompt "" and be done with it. I wish they allowed for other harnesses.

> --system-prompt ""

Doesn't the model need at least a basic system prompt to understand what tools are available?

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#53
What really burns tokens is sub agents. I once gave Claude Code a pretty big task, and it immediately launched 7 sub agents which burned through my budget before even one of them was finished. Tried again 5 hours later: same result.

If I let the main agent do the same task sequentially, it was no problem at all. I don't know if it's really just communication and orchestration that makes sub agents so inefficient, or if Anthropic figured that most people using sub agents pay per token on a big corporate account, so this is an easy way to make more money from tokenmaxxers.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#54

My opinion is that claude code uses more tokens simply because Anthropic makes more money that way and forces people into their subscriptions. This is supported by the fact that they won't let you use your sub on a different coding agent. I use pi btw.

You're making the opposite argument. Anthropic is incentivized to use less tokens in Claude Code because people are paying a fixed monthly fee for subscriptions.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#55
post #6

And pi agent is even less. The entire agent system prompt can be seen here: https://github.com/earendil-works/pi/blob/main/packages%2Fco...

If you really want a minimal agent that you heavily customize, just skip pi (130+ transitive dependencies on the "minimal" pi-coder package) and write your own. You learn a bunch, and it's not hard. You can even ask another LLM to help you get started.

I wrote my own harness in Emacs and it’s completely ridiculous how well it works. Auto-compact is the only missing feature on my list. Claude‘s approach, if I understand it correctly, invalidates a lot of cached context, and I‘m thinking about a more cache-friendly strategy.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#56

My opinion is that claude code uses more tokens simply because Anthropic makes more money that way and forces people into their subscriptions. This is supported by the fact that they won't let you use your sub on a different coding agent. I use pi btw.

I thought I read somewhere that according to filings for going public, subscription revenue is tiny… like 5%. Edit: consumer Claude subs are the 5%. I’d bet most all of CC subs lump in under enterprise. - API & Enterprise: 75% to 85% of total revenue. - Business Subscriptions: Roughly 10% to 15%. - Individual Subscriptions: About 5%.

The vast majority of my company's enterprise plan use is through Claude Code even though we have access to the API and could be using OpenCode instead.

I don't fully agree with the premise that they intentionally increase system prompts, but the enterprise plan usage is going to make that a huge income for Anthropic.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#57
I feel like this article isn't saying much. Even with tools disabled, Claude Code still has a crap load of commands and other things that Claude (the model) should know the availability of since it's optimized for them. All of that has to be disabled if this is to be a real harness comparison. And of course the system prompt can be completely replaced, making it a no-brainer to use a more minimal prompt similar to OpenCode. And beyond that nothing else really matters because the rest (cache behavior, etc) lies with the provider's platform, not the harness.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#58
post #54

My opinion is that claude code uses more tokens simply because Anthropic makes more money that way and forces people into their subscriptions. This is supported by the fact that they won't let you use your sub on a different coding agent. I use pi btw.

You're making the opposite argument. Anthropic is incentivized to use less tokens in Claude Code because people are paying a fixed monthly fee for subscriptions.

Nope, that’s not true, because they want you to pay for the higher subscription bracket.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#59
post #5

This isn’t limited to large system prompts. Coding-agent harnesses are also becoming more aggressive about using tools, even for trivial requests. In our tests, prompts such as “Hey” or “commit” sometimes triggered 30+ tool calls: https://quesma.com/blog/the-true-cost-of-saying-hi-to-an-ai-... Tokenflation seems very real: the number of tokens consumed by simple tasks keeps increasing.

> prompts such as “Hey” or “commit” sometimes triggered 30+ tool calls

I read that this is because it wastes time looking through past conversations and other context to figure one what you might want it to do - a less ambiguous prompt would be better.

Re: Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k

#60
post #53

What really burns tokens is sub agents. I once gave Claude Code a pretty big task, and it immediately launched 7 sub agents which burned through my budget before even one of them was finished. Tried again 5 hours later: same result. If I let the main agent do the same task sequentially, it was no problem at all. I don't know if it's really just communication and orchestration that makes sub agents so inefficient, or…

for subagents to be cheap/effective, you have to specify the size of those subagents; i.e. right now by default 5.6-sol spawns many 5.6-sol subagents. 5.4-mini as subagent saves me tons of tokens. 5.6-sol audits the work before accepting it, so there's not really a quality issue.
Post reply on HN