Vibe Coding
Pattern: Spend Control Has Become a Correctness Surface, Not a Reporting One
This week's releases treat cost as something that can be silently wrong. Claude Code 2.1.239 folds the 1.1× US-only-inference premium for data-residency workspaces into `/cost`, the status line and `--max-budget-usd`, fixes a proxy bug that doubled billed calls without an error, and makes the retry watchdog abort on spend limits rather than wait. Outside Anthropic, loop-engineering ships `loop cost` to price a schedule before you run it and LeanCTX ships a live token-savings dashboard. The shared assumption is that an autonomous agent will happily spend money on a bug, so the budget has to be instrumented at the same fidelity as the output.
↳ Follow the thread