Somewhere in last month's bill is a session that rewrote the same migration four times. You paid for every attempt. You'd like to know how many sessions like that there are, and what they have in common.
The Problem
Rework is the most expensive thing an agent does, and the least visible. A session that plans, makes a change and tests it costs a fraction of one that guesses, breaks something and starts over. On a usage page, both are just tokens.
How It Cascades
The same failure pattern repeats across engineers because nobody sees it twice.
Engineers blame the model, switch to a pricier one, and the rework gets more expensive.
Review time grows as pull requests arrive with churn the agent created and undid.
The Insight
Rework leaves a trail. Each session either redid work or it didn't, and the reason is usually in the session itself: no plan, no test, a missing instruction, an unclear ask.
The Solution
VibeCheck reads every Claude Code, Codex and Cursor session and records whether it planned, tested, reviewed and reworked, each with a one-line reason. In Sessions, filter rework to high, sort by cost, and the most expensive rework is at the top. Open one to see the steps, the reason for the rework and where the engineer corrected the agent. Narrow by repo, team, model or kind of work to see whether the pattern belongs to a codebase, a tool or a habit.
The Outcome
You find the two or three patterns behind most of the rework spend, fix them where they live, and compare what heavy-rework sessions cost this month against last.