Skip to main content

Release 0.1.133

Agent costs now include failed and cancelled runs and the work of subagents, projects that merge through pull requests no longer have Repave write configuration to the base branch, Repave IDE can push its own branch, and the Repave CLI stays signed in.

Upgrade notes​

  • Two database migrations, applied automatically by the upgrade.
  • Some costs are corrected on first start. Runs that were recorded at a guessed price — including Claude Sonnet 5 runs recorded at 1.5 times their cost before 0.1.123 — are repriced the first time the upgraded app starts, so those totals may drop. Nothing to run by hand.
  • Pre-upgrade backups belong to you. When you run the upgrade with sudo, the backups it writes are now owned by your own user rather than root, so you can delete old ones without sudo.
  • .env and docker-compose.yml: nothing to edit.

New​

Push from Repave IDE. Run /repave:push-to-remote in Claude Code (/push-to-remote in Codex) to push the branch you have checked out, exactly as the feature's or worktree's Push button does. Anything uncommitted is committed first, and you get one line per repository. The same push is available as repave push in the terminal, with --preview to see what would happen first.

Configuration arrives as a pull request in pull-request merge mode. BDD and UAT test configuration, preview dev configuration, sample data seeds and the design system now arrive as a pull request of their own from a repave-platform/ branch, instead of being written to your base branch. A feature's BDD run waits until the BDD configuration pull request has merged, and says which one to merge.

The Repave CLI stays signed in. After repave auth login, the CLI renews its own sign-in, so you stay signed in for as long as you use it at least once every 30 days.

Improvements​

Costs cover failed and cancelled runs. A run that fails or is cancelled is now counted. When it was stopped before it reported its cost, its work up to that point is estimated at list price.

Token counts include subagents. A run's token counts now cover everything its cost does, including any subagents the agent handed work to.

Undoing a model or advisor change brings back the advisors it turned off, as long as you have not saved yet.

The Start preflight dialog says why a preflight could not start — for example, an application shell that still has to be implemented and merged — instead of asking you to try again.

/repave:dev-start uses the dev servers you already started in this checkout, instead of stopping at "port already in use".

Fixes​

Saving project settings could stop Repave IDE sessions without asking, or ask again for a change already saved. Replacing the project's API key ended open terminals unasked, and every later save in the same visit asked again. Now Stop running Repave IDE sessions? appears only for a save that actually stops sessions, with the number open.

A prototype change could not start while the feature's worktree held files of your own, such as settings Claude Code leaves in Repave IDE. A change now builds on top of them, and a change that fails keeps every file in the worktree.

The application shell's pull request could include thousands of installed dependency files. The shell's commit now holds only the shell's own changes.

On the Memory page, the first click on Next could jump back to page 1.