Anthropic published the token economics of Claude Code, and 247 HN points called it a product failure

Output tokens cost roughly 5x input, because decode is sequential. Cache reads cost 0.1x input price. The prompt cache expires after 1 hour on subscriptions and 5 minutes on API keys.

Those three numbers are the whole post, and Anthropic put them in one place for the first time on August 14. Anthropic The guidance that follows is concrete: run /clear between tasks, fix your model and effort level at session start so you don't bust the cache mid-conversation, @-mention files to skip a Read call, add quiet flags or hand noisy commands to subagents, and run /context in a fresh session to find tool definitions you're paying for on every turn and never using.

That last one is the highest-value five minutes in this newsletter. Go run /context right now. Every MCP server you connected six months ago and forgot is sitting in your system prompt on every single request. I found tool definitions I'd stopped using in April.

The 1-hour subscription cache TTL is the number that should reshape how you work, and it cuts the opposite way from how people read it. It means a session you come back to 45 minutes later is still cheap. It also means the fifth hour of a long session has rewritten the cache several times. Pace your sessions against that window rather than against your own attention span.

Now the counter-argument, because it's a good one. The 247-point HN thread reframes the whole post as a product failure rather than a tutorial. Commenters reached for the iPhone antenna comparison: you're holding it wrong. Their argument is that these optimizations should be automatic, and the harness should do them. Hacker News

The concrete grievances are hard to wave off. A documented 1.6M-token cache write exceeding $100 in a single session. Multiple reports of cache bloat during normal workflows with no user action that caused it. And the 5-hour usage limit, which reads badly next to competitors resetting every two days.

I'm mostly on the users' side here. If /clear between tasks is correct 95% of the time, the harness knows when a task ended better than I do. But the most useful thing to come out of that thread isn't the complaint, it's a workaround: use a /handoff skill that writes a portable summary roughly every 20 messages, instead of running /compact on a long session. A summary you can read and edit beats a compaction you can't inspect. I've switched to this and my sessions restart cleaner.

Connect this to story 5. Anthropic is telling individual developers to measure cost per task on the same day Canva told public markets it couldn't.