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 [email protected] 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.

I work on Claude Code. Prompt suggestions aren't being used to collect preference signals. We built this feature purely to help you stay in the flow, or for people who are returning to the session after a while and may need a little reminder on what a next step could be. We do see how many suggestions are accepted, but that's only so we know how helpful this feature is overall! (We tried to strike a balance by not making it "autocorrect", so it's more of a grayed out suggestion that can be typed over. It can always be toggled on/off in settings if you don't like it.)