Opus 5.5 cuts cache reads 60%: Addy Osmani breaks down real Claude Code task costs
ClaudeDevs · x · 2026-09-26
claude.dev published a deep dive on what Opus 5.5's price cut means for real Claude Code tasks: 20% cheaper input/output tokens and 60% cheaper cache reads versus Opus 5.
Key points:
- Task cost is driven by turns, cache reads, and output token type — every turn resends the full conversation, so a retry costs more than any token-saving setting.
- Same per-token price can mean very different task costs depending on how many turns/retries a model needs; price tasks, not tokens.
- The post quantifies tradeoffs (lower effort, smaller model, less context) and ships a calculator so you can estimate your own typical task costs from /usage data.
More from coding & agent
- Claude fumbles a payment task: wrong browser profile, never tried computer use — trq212 · 2026-09-26
- Blender agents meet fal's H3 Max: 3D previs turns into photoreal video — gorkem · 2026-09-26
- Claude Computer Use Team Asks Users for Specific Failed Tasks to Fix — trq212 · 2026-09-26
- DavidKPiano recreates Apple's 'Wonderful Tools' animation using Opus 5.5 — DavidKPiano · 2026-09-26
- Full Opus 5.5 SEO/AEO Automation Loop: From Keyword Research to Winning ChatGPT Answers — PrajwalTomar_ · 2026-09-26
- Multi-Agent Handoffs Keep Dropping Constraints: What Actually Crosses Over? — Asly97 · 2026-09-26