Skip to main content

Release 0.1.129

A feature's target-stack prototype is now the start of its own branch, and a new project builds its application shell before its features. Administrators can cap what an implementation run spends, and you can see the memory each Repave IDE session and agent run is using.

Upgrade notes​

  • Five database migrations, applied automatically on upgrade.
  • Rebuild your target-stack prototypes. Prototypes used to live on a shared prototype/main branch; they are now built on each feature's own branch. After the upgrade, every existing target-stack prototype reads "Prototypes now build on the feature branch; build again to restore the preview." Build it again from the feature's Preview tab. The prototype/main branch in your repository is left as it was. Prototype jobs still queued or running at the upgrade are cancelled and stay on the Jobs page.
  • Repave IDE sessions get 8 GiB of memory by default. Every project still on the previous default of 4 GiB moves to 8 GiB; a limit you set yourself is kept. A running session keeps its limit until it restarts.
  • Existing projects are not held to the new shell rule. Their features can still be implemented before the shell is merged.
  • Upgrade the agent runner image with the app. It now reports each agent's memory.
  • .env and docker-compose.yml: nothing to edit.

New​

Prototypes on the feature branch. A feature's target-stack prototype is now the first work on the feature's own branch, and implementing the feature continues from it, replacing its placeholders rather than building the screen again. Prototypes of different features no longer wait for one another. On the Preview tab, Implementation shows the branch running on your stack — first the prototype, then the implementation — with Rebuild from the design and Remove prototype while it holds only the prototype. The features list shows Prototype for those features. A feature cannot be merged while a prototype placeholder remains.

Implement the application shell first. On the Navigation & Shell page, Implement shell builds the chosen shell design on your stack and lands it on the base branch, by pull request or after you review it and click Merge, depending on how the project merges. In a new web application project, features can be implemented once the shell has merged, so every screen is built in the same frame.

Implementation budgets in the admin portal. A new Budgets page decides whether users set a budget when they start an implementation run, and can set a maximum no run may exceed. The limit holds however a run starts, continues or resumes. With a maximum set, implementation runs must use a Claude model, because spend can only be measured for Claude.

Memory on the Repave IDE page. Each session under Opened IDEs shows its Editor and Docker memory against their limits, and says Out of memory when a process was killed for memory, naming the limit to raise. Each session's Stop, Restart and Open in Repave IDE are now on its row.

Memory on the Queue page. A running agent shows Agent and Docker memory meters, and a job that ran out of memory keeps an Out of memory badge after it ends, saying how high memory went and how many processes were killed.

Improvements​

Visual revisions are checked by a build. A revision that changes only how something looks — a colour, spacing, a layout — no longer fails for want of a scenario to run; a successful build is its check. With the browser on, which is now the default for the Implementation revision agent, the agent starts the app and looks at the page it is changing.

Fixes​

The Repave IDE browser panel got stuck when a page opened a dialog, and Reconnect waited on "Starting the browser…" forever. Alerts, confirmations and prompts now appear in the panel for you to answer. A page that stops answering says Page not responding, with a reload button, and the tabs stay so you can switch to another. A page the agent has given a fixed size is shown whole, scaled to fit.

A colleague's outdated comment blocked the shared prototype review, and nothing in the panel could clear it. Anyone who can edit the project can now delete any open comment, and Keep and Discard all act on everyone's; only a comment's author can change its wording.

A duplicate Figma link above the prototype tabs covered the tabs with its tooltip. It is gone; Open in Figma in the Design pane is the way into Figma.