Skip to main content

Release 0.1.126

You can now run, scan, adjust and revise a feature's implementation from its Preview tab, the same way you already review its prototype. Agent runs and Repave IDE sessions now share one runtime image, so there is one airgap bundle to download and no toolchain setting to get right. Repave can also be connected to Claude and other MCP clients, and agents can use Jev for small judgments.

Upgrade notes​

  • Eight database migrations, applied automatically on upgrade. All of them add tables or columns; nothing existing is rewritten.
  • One airgap bundle. The separate -airgap-session-bases.tgz bundle is no longer published; everything is in the core bundle.
  • .env: nothing to edit. The upgrade removes the SESSION_BASE_* keys an earlier release wrote, and prints a line naming each one. The old Repave IDE images are removed only after the upgraded stack passes its health check, so a rollback still works.
  • Client toolchain overlays: there is now one overlay, declared as AGENT_RUNNER_IMAGE_OVERLAY, and it serves agent jobs and Repave IDE sessions both. A session overlay declared on its own is carried over as the agent runner's. Load the 0.1.126 overlay image as usual.
  • docker-compose.yml loses the three session-image variables; use the file from the bundle.
  • Optional: TYPESAFE_API_KEY in .env turns on Jev for every project. Leave it unset on an airgapped install; nothing else changes without it.
  • Agents now run on a Debian base. A project worktree whose node_modules an agent installed before this release may hold packages built for the old base; the next npm install replaces them, and the test runs agents start already do that. A build that fails with Cannot find module …-linux-x64-gnu before then is the sign.
  • Installing on RHEL 10 with SELinux enforcing is now supported by the Docker bootstrap script.

New​

Preview a feature's implementation. The feature's UI Prototype tab is now called Preview, and it has an Implementation view that streams the running implementation next to the design. It runs in dev mode on the prototype's configuration, and starts when you open it. A merged feature shows the branch it merged into.

Adjust, scan and revise the implementation in place. The Implementation view has the same review tools as the prototype: Adjust to pin comments on the screen, Accessibility to scan the screen you navigated to, and Revise implementation to send your pins to the agent, which fixes them on the feature's branch and reports back per pin. Restart and Stop are in the Env menu, and Write Tests sits in the same toolbar.

Adjust keeps the design and the scenarios in step. When an Adjust run changes what a screen looks like, it now writes that change back to the selected design option — HTML or Figma — and to the feature's To-Be scenarios. Only the scenarios it changed lose their approval. Anything that could not be written back is noted on the pin.

Connect Repave to Claude and other MCP clients. Paste your Repave address into the client and click Allow; there is no token to copy. The connection is read-only: feature status and what AI runs cost. Manage or revoke connections under Connected apps.

Jev for agents. With a TypeSafe key in Project Settings → Agents, agents can ask Jev quick judgment questions instead of spending a whole turn on them. The Costs page shows Jev usage in tokens. Without a key, nothing changes.

Get back to where you were. The project sidebar has a Recent section with the last five pages you opened, and the feature lists show your five most recent features at the top.

Help and Support. Help is in the project top bar, and every footer links to support.repave.ai.

Your own preview. Each reviewer now gets their own browser in the target-stack preview, per feature — you no longer drive each other's screen or share one sign-in to the previewed app.

Improvements​

Repave IDE, by one name. The editor is called Repave IDE on every screen, button and message, and its browser tab says so too.

No toolchain setting. A provided codebase no longer declares a toolchain, and Repave IDE and the target-stack preview are no longer refused over one.

Repave IDE sessions see the prototype live. A session gets the project's prototype as a read-only folder that updates as the prototype changes, instead of a copy taken when the session opened. Opening a feature whose scenarios are approved also writes its .feature file if the workspace has none.

Clearer prototype controls. Restart, Reinstall and Stop are in an Env menu beside the preview's status; Rebuild is now Revise prototype and Remove is Remove prototype.

Tidier feature pages. Panels no longer repeat the tab's name as a heading, Generate To-Be sits on the scenario search row, and every checkbox is the same, larger size.

UAT verification results show up as test results. A feature verified in UAT now has a Test Results tab with its scenarios, as other test runs do.

Editing one scenario from the CLI keeps the others approved. Changing a scenario withdraws only that scenario's approval, not every approval on the feature.

No more false "Outdated" badge on the UI Prototype panel; an outdated design still offers Regenerate.

Fixes​

Repave IDE could not install packages after the Implementation view ran. Files the preview wrote into the feature's workspace were owned by root, so the session's npm install failed. They are now owned by the session's user, and existing workspaces are repaired on the next start.

UAT verification ran the wrong scenarios for features with non-Latin or punctuated titles, and the test command did not target the feature at all. Both now use the feature's real file.

After an upgrade or restart, the streamed preview reported "the preview browser did not become drivable within 30s". It now reconnects.

Typing into the streamed preview after clicking it did nothing, a maximized preview whose app stopped could not be restored, and dragging to select text lost the selection. All fixed.

The browser was missing in Repave IDE sessions, so browser tools in the IDE had nothing to drive.

Security updates, including a critical fix in the web framework's image handling.