Category
65 posts in this category.
The Cost column in ccusage is a counterfactual: what your tokens would have cost at pay-per-use list prices, computed locally. On a Claude subscription it is not your bill, and ccusage's own introduction and Anthropic's own docs both say so. A field log on what the number measures, where the caveat is written, and where it is missing.
OpenCode Go's own page states usage limits as requests per five hours, per model, across fourteen models running 110 to 45,300. The two third-party pages that rank for the term describe the same plan as a three-tier dollar budget on a lineup that has largely turned over. A field log on which source to trust and why.
Agent teams are off by default in August 2026, and turning them on also changes how ordinary subagent delegation behaves. A documentation field log on the env var everyone writes wrong, the 7x token figure nobody quotes correctly, and the five minute cache bucket.
Every comparison ranking for this query calls goose Block's open-source agent. Block donated it to the Agentic AI Foundation at the Linux Foundation in April 2026, alongside Anthropic's MCP. A field log on what that changes and what it does not.
Every explainer quotes a 200,000-token ceiling. Anthropic's own docs say the auto-compact window is a setting you choose, from 100K to 1M, and that Sonnet 5 compacts at about 967K. The popular fix is to disable auto-compact. There is a flag instead.
Every page-one comparison treats this as a choice between two products. Google's own model docs say Antigravity offers Claude Sonnet 4.6 and Opus 4.6, free tier included. That makes it a harness comparison, not a model one, and it changes the answer.
Most of page one still compares Devin the autonomous cloud agent against Claude Code the terminal agent. I opened both 2026 pricing pages and the billing docs, and two of the claims everyone repeats are out of date.
I built the same rate-limiting feature twice, both inside Warp. Warp's own docs argue you should switch off Claude Code, then document running it inside Warp. Here is what that actually means for a solo dev in 2026.
I built the same CSV-export feature with GitHub Copilot and Claude Code from the same commit. The code came out close. The pricing shape is what actually decides it.
I ran the same task in Aider and Claude Code on the same model. The code converged; the workflow did not. The real split is where your undo lives: git or the agent.
Claude Code code review is really two products with one name: a Team-only GitHub PR service and a free local /code-review command. I ran the local one on my own agent-written code for two weeks. Here is what it caught, and the REVIEW.md trap nobody mentions.
I shipped the same feature twice, once in Kiro and once in Claude Code. The code converged; the workflow did not. How I route between spec-driven and terminal-native in 2026.
