Costs

What the work spent. Whether this is visible is a deployment setting — the cost view is hidden by default, so if you cannot see it your operator has not turned it on.

What is counted

Agent spend, costed against the rate card of the provider that actually served the call. A project running Claude through one route and another model through another is costed per provider rather than at one blended rate that would be wrong for both.

This includes the agent you drive yourself in a Repave IDE session, which appears in its own Repave IDE column. A session opened on a feature's worktree is counted against that feature; one opened on the modernized checkout is counted against the project, as is work in a worktree shared by a module's features — that session does not belong to any one feature, so its cost is not attributed to one.

Sessions are counted from the release that introduced this onwards. Repave IDE work done before then is not included, so a feature built by hand earlier will read cheaper than a comparable one built today.

Per feature, per stage

A feature's cost is attributed to the step that spent it, and broken down by pipeline stage on the cost view. That breakdown is the useful part. "This feature cost X" tells you little; "most of it went on review cycles" tells you where to look.

Cost can also be split by model, which is how you find out whether a more expensive model is earning its place on a particular stage.

The features table

Every feature with its cost, paginated, showing each feature's status alongside. The status column matters when reading the numbers: a feature that cost a lot and is failed is a different story from one that cost a lot and is merged.

The table stands alone — it does not require the rest of the view to make sense — and it downloads as an Excel workbook when you need the numbers somewhere else.

Controlling spend

Costs are a report, not a control. The controls are elsewhere:

• A per-run budget stops an implementation before it overspends, rather than after — see Implementing a feature.
• Model and advisor choice per agent, and prompt cache lifetime, whose cost the settings table shows you directly.
• Validation passes are capped at a configurable number of agent calls.

See Project settings.