FINOPS

A trending Codex SQLite WAL bug is a useful warning for every local coding agent: logs, disks, background processes, and telemetry paths need budgets too.

A $500M accidental Claude bill and an open-weights model beating GPT-5.5 at one-sixth the cost point to the same conclusion: the margin is moving to the layer that decides when to use which model for what. Here is how routing and orchestration differ, and how to cut your model spend.

Uber burned through its entire 2026 AI tools budget by April. Microsoft is canceling Claude Code licenses company-wide. What enterprise teams can learn from the first major AI coding tool budget crises.

The viral DN42 AWS bill story is funny until you realize the missing primitive: infrastructure agents need hard cloud-spend guardrails before they touch real accounts.

AI coding agents have crossed from demo to daily workflow. The next bottleneck is not demand. It is cost attribution, budget gates, and workflow design that keeps agent fleets from turning useful work into surprise spend.

Anthropic's June 15 Agent SDK credit split is not just a pricing tweak. It is a signal that autonomous coding workflows need separate budgets, lanes, and receipts.

The latest Claude Code cache-burn debate is not just a quota complaint. It is a reminder that coding agents need cache-hit telemetry, spend ceilings, and repro-grade usage logs.

Two quality-of-life tools we built this week for Claude Code daily drivers: a SKILL.md linter and a VS Code status bar that shows live LLM spend.

Five managed-agent providers, five pricing models, zero unified cost attribution. If you're running agents overnight, you need FinOps you don't have yet.