HN

Comments (98)

• Menu

  AlexErrant
  While we're modding Claude Code, Anthropic includes your email in the system prompt and Opus _constantly_ includes it in request headers.https://www.reddit.com/r/ClaudeCode/comments/1xhqvzn/opus_55...You can remove it with a simple plugin https://github.com/AlexErrant/claude-code-no-email/blob/main...
• Menu

  franticgecko3
  Claude Code burning a large amount of tokens for no good reason is a headline we've seen more than a few times now.Time to start questioning the motivations of model providers shipping their own harnesses.
• aidos
  I’d like to take a moment to appreciate how horrible (but crafty) this patch is. Calls to setTimeout globally are patched to check to for this code before being honoured or discarded.There’s something reassuring about seeing the true hacker spirit still at work here.I approve.https://gist.github.com/flamerix-ai/c3905705cc4205e5de3011fa...
• Menu

  HeavenFox
  If they are literally sending the entire transcript and asking for a summary, wouldn't almost all of the tokens be cache hit, and therefore fairly cheap?
• Menu

  gym
  I was surprised the usage issue wasn't mentioned here before this based on my searching on hn.algolia.I'm on pro. Two days ago, 100% 5 hour was using 25% of my weekly. Today, 100% 5 hour is like 13% so something was fixed.
• user43928
  "The agent's own model", huh?I hope Anthropic's next model is capable of better writing.I find the way it adds this unnecessary "own" very grating in explanations.For example: "Two benchmarks, each with its own score".Of course the author could also just write at least the summary himself.
• dozerly
  This is the harness’s job. Incentives are not aligned for inference providers to own the harnesses.
• Menu

  jakozaur
  I tested it, and it looks real but more nuanced. It is just for subagents; workflows do not seem affected. I guess many new users prefer workflows (ultracode), so the impact is less than the report suggested.Moreover it is mostly cached reads, so subagents with short context cost little, while long-context ones cost much more.In my Claude Code sessions, it looks more like ~8% at most.
• Menu

  messh
  Bloat. I like Pi much better with it's minimalism
• creamyhorror
  Background agents only have 5 minutes' cache TTL, but I'm guessing this doesn't help extend it (not that it would be too useful anyway, especially considering the extra burn).Also, the claim "15-20% of your tokens" seems unclear; of all tokens, or of tokens spent on background agents? Poorly edited AI writing strikes again!
• _boffin_
  Just looked and we're burning around ~3%, but that's across everything / everyone.
• anon
  undefined
• ab_wahab01
  Does this happen in the VS Code extension? or only in the terminal?
• Menu

  poisonborz
  Claude lovers tend to be either early adopters not well informed/lazy to experiment ("why, it's still the best, right?"), or millionaires or devs with unlimited budgets, who often ask on HN "why would you use anything else than Opus on xhigh".I was handed 150$/mo budget and no subs, and while it was frustrating at first, with better tooling, context management and especially OAI models it's a breeze now and not even using 70% mostly while achieving a lot in a small team.Having limited resources teaches you a lot.
• xyzsparetimexyz
  Claude code has to be the worst harness I've ever used. Has anyone figured out how to rip the subscription auth/verification out so that it can be used within Pi yet?
• Menu

  nikolay
  Opus 5.5 burns tokens like there's no tomorrow! Meanwhile, GPT 6.1 Sol on Extra High feels unlimited! Opus (on Max 20x) munches my weekly quota in a day, or two at best. Meanwhile, working with Codex and reviewing with a $50/mo Muse Code Wonder Full seems like it can go own forever (on the same codebase, the same skills, etc.) I am highly disappointed by the overly glorified Opus and Claude Code in general - there's no commit in which Codex or Muse Code or GitHub Pilot don't find critical flaws! I have long sessions of Claude Code having over 100 review cycles of Codex and still not addressing all the valid issues that Codex finds in Claude Code's work! Claude Code keeps injecting British English into prose and identifiers with nothing being able to stop it! Of course, there are almost never resets for Claude Code either - they would rather me focus on Codex being my primary and Claude Code being the reviewer (it works much better than in reverse). Anyway, enver trust a single model! Always review with another frontier one!
• Menu

  apt-apt-apt-apt
  At least they seem to have fixed their free-revenue feature-bug, where they randomly invalidate your cache (~$8 a pop (turn))
• leroman
  At the base there is a conflict of interests- what we pay for
• quantbuilder
  i think its not the status line at the bottom of the terminal, but actually the few words summary claude generates for each background agents in the agents panel. so if we mostly run one plain session we wont pay for this? i do run claude code with disableAgentView on in my settings. does anyone know if that helps to stop the summary calls or just hides the panel?
• z3ratul163071
  those i guess are all cache hits.
• rurban
  That's why people are using pi, not Claude. What a waste of money
• emsign
  This is fraud. Unknowing to its customers a company is running a daemon that wastes a commodity it sells to said customer.
• Menu

  tluyben2
  I now run Jev in front of claude code and the results so far have been very good. It picks Haiku far far more often than I would think to use it and it works very well.
• nullbio
  Not good. Please fix.
• rsalus
  does this happen for Claude Desktop too?
• simianwords
  Isn’t this prompt cached? Then it’s not that big of a deal
• raverbashing
  Another reason why CoPilot seems more "honest" than CC
• moezd
  It's how they finally become profitable: You burn through your token quotas so you have to buy them per request now. Oh, and also Enterprise seats are selling like bubble gum.It's the same addiction script again and again.
• NikZaal
  Claude Code's (CC) status summaries used 16.4% of our token spend in a week! We have investigated a source of overhead in CC: it's an agent_summary query that calls your current session/subagent model approximately every 30 seconds for a few words in CC’s status line.Our DRIM system flagged the anomaly in CC's OTEL traces. Grouping requests by query_source showed that over one measured week agent_summary accounted for: 16.4% of total estimated spend (versus 15.7% for the main conversation), and 19.7% of all API requests with approximately 9,000 input tokens per output token.Most requests reuse the prompt cache, but repeatedly reading a large cached transcript still has a cost. Longer contexts and more concurrent agents increase the overhead.We couldn’t find a supported setting that disables only these summaries while preserving background agents and forks. Disabling those capabilities also stops the summaries, but changes the workflow we want to keep.Our workaround is a small Bun preload that intercepts the summary timer without modifying the CC binary. It identifies the timer callback by source-text anchors and leaves other timers alone.In controlled tests on Linux (from ver 2.1.257 to 2.1.312), the same workload produced five summary calls without the hook and zero with suppression enabled. On our current production setup, agent_summary calls remained at zero with the hook enabled. Background agents and forks continued running. The only visible change was that their generated status summaries stopped updating.The workaround depends on implementation details. An update can break the callback matching and silently restore the requests. macOS and Windows are untested. If someone could help us with testing there, it would be much appreciated.If you want to try it - the script, full technical explanation, test results, and installation instructions are on GitHub: https://gist.github.com/flamerix-ai/c3905705cc4205e5de3011fa...
• appsbymo
  [flagged]
• lostsock
  [flagged]
• vinaygundeti18
  [flagged]
• mokto
  [dead]
• Menu

  edwinarbus
  I work on Claude Code. You've got the basic mechanism right, but to be super clear, this only applies to background agents that are actively working. They get a summary call about every 30 seconds, and idle background agents don't. These summaries are used for both you and Claude Code to track what each background agent is working on, without reading transcripts.Your 16.4% sounds like it was for a team running mostly background agents, and doesn't seem like a typical session. (Feel free to send me the session ID at edwinarbus@anthropic.com and we can dig further.)Last week, across Claude Code users who send us telemetry, agent_summary was about 2% of cost at API list prices and just under 4% of requests. In the terminal, where nearly all of these calls happen, it was about 6% of cost.That said, we agree that's a lot for a status line. We just rolled out a fix for the most expensive case, summaries that miss the prompt cache (2.1.311+), and right now we're working on a much cheaper mode that sends short notes to a smaller model instead of the full transcript.
• digitaltrees
  It’s almost like they are trying to go public. Burn those tokens.
• helsinki
  I’m sure they release a decision model that alleviates this problem in due time.
• Menu

  hypfer
  With the ever-increasing amount of paper cuts one gets from using their products, I wonder how long this will really go on?After all, for most of the work people seem to be doing daily, Claude kinda isn't.. necessary? In fact, for a lot of tasks, not using it leads to better results in my experience.There are things that only it can reasonably accomplish, but if every interaction with it hurts you in various ways (like this one), then, eventually, I do not see that working out for them anymore.But perhaps this is just a way to push the numbers a bit further up for the IPO? That would make a lot of sense to me.