Skip to main content

Release 0.1.130

Budgets now cover every agent, not only implementation, and preflight asks a feature's questions once. Repave IDE gains worktrees for changes that are not a feature, and the MCP server can say who spent what and how many rounds a feature took.

Upgrade notes​

  • Five database migrations, applied automatically on upgrade. Past runs are attributed to the person whose prompt started them; runs with no recorded prompt are reported as unattributed.
  • No new limits apply until you set them. The new per-feature and per-project maximums start off.
  • Upgrade the agent runner image with the app. It now carries the skills agents load.
  • .env and docker-compose.yml: nothing to edit.

New​

Budgets for every agent. Every agent job — implementing, fixing, merging, opening a pull request, revising, writing tests — can now have a budget per run, set per agent in the new Budget column of the project's agent defaults. On the admin portal's Budgets page an administrator can also set a Maximum per feature and a Maximum per project, each counting everything spent over its whole life. Work a budget stops is kept and says which budget stopped it: Reset and continue restarts a run, Raise budget… on a feature's or module's page raises that feature or module, and only an administrator can raise a project, from the banner on every page of the project or Raise… on the Budgets page.

Preflight runs once per feature. Every later Preflight or Implement keeps the answers you already gave, whether the earlier attempt was paused, discarded, failed or finished, and whether it was the feature's own run or a module run. If nothing preflight reads has changed, nothing is asked and Implement starts straight away; if something has, preflight asks only about that change. The carried answers show as a Carried over round. To answer everything again, start Preflight and tick Ask every question again. After the upgrade, the first launch of a feature that already has answers runs one short check, because earlier attempts did not record what preflight read.

Worktrees in Repave IDE. For a change that is not a feature — a dependency bump, a build fix — click New worktree in the Worktrees section of the Repave IDE page, open it in Repave IDE, and land it with Create PR or Merge to the integration branch. Each row shows how far the branch is ahead and behind and offers Push, Pull, Merge from and Delete. On a combined workspace, worktrees are where such a change is made, with one pull request per source repository it touches.

Who spent what, over MCP. Ask your assistant how much a person spent, for example in Repave IDE last month, or how many rounds of implementation and prototype revisions a feature took. Every run now records who started it. Only the project owner sees other people's spend; anyone else sees their own and everyone else's combined.

Test data for a merged feature. On a merged feature, the Implementation pane's Preview environment menu offers Reopen and add test data…. After one confirmation the feature is reopened, its implementation starts, and the test-data dialog opens; once the data is committed the feature is Implemented again, ready for Create PR or Merge to Repave Branch.

Improvements​

The full Implement dialog after preflight. Implement after a preflight now offers the same choices as everywhere else — verification, model, spend limit, reference images and additional instructions. Start preflight with Start implementation when preflight is done asks for the verification and spend limit up front.

Open a module's worktree from the module's page. Open in Repave IDE on a module's page opens the same session as the module's card in the chooser and its features. It stays disabled, and says why, until the module's first implementation run creates the worktree.

See which skills an agent had. In Agent Logs, the Session started entry counts the skills the agent was given; Show skill names lists them.

/repave:plan is gone from the Repave plugin. /repave:implement works from the approved To-Be scenarios and the preflight decisions, so there is no plan file to write first.

Fixes​

Target-stack builds failed at the very end, losing the agent's work, in a project whose .gitignore lists .mcp.json. They now commit.