Release 0.1.138

A project assistant you can chat with about the whole project, a record of what every agent run was given and changed, project documents written in your organization's own template, and a daily email digest of what is waiting on you.

Upgrade notes​

• Database migrations run automatically during the upgrade. They add the project assistant, agent run records, document types, the email digest, per-project local VS Code, and a record of where delivered features landed in your repositories. No existing data is changed, except that the Out of memory meters' old readings are kept as limit hits with an unknown kill count.
• The email digest is on for everyone after the upgrade. Each project member gets one email a day at 08:00 in their own time zone, and only on days when something is waiting on them or moved. It needs email set up in the Admin portal; without it, nothing is sent. Each person can change or turn it off from Email digest in the account menu.
• The gateway image moves to eceasy/cli-proxy-api:v8.0.28. If your .env sets CLI_PROXY_IMAGE (every airgapped install does), change it to eceasy/cli-proxy-api:v8.0.28, making that image available to the server first if it has no internet access. The upgrade does not change this line for you, and the older gateway fails some Gemini runs.
• The upgrade unpacks old agent transcripts from earlier upgrade backups into the data directory, so runs from before this release get as full a record as possible. This needs some free space on the data volume. If it cannot be done, the upgrade prints a warning and carries on; the backups themselves are not touched.
• docker-compose.yml: nothing to edit beyond the gateway image above.

New​

Project assistant. A chat beside every project page: ask it about the project, or ask it to change a scenario, a prototype's wording or a file in a feature, and take any change back with Undo. It knows which page you are on, can pull, push and open pull requests for you, and keeps your past conversations. It is off in every project until a project owner turns it on in Settings → Agents.

A run's record. An agent log for a job that works in a feature's worktree now has a Record tab beside Conversation: the prompt, model and versions the run used, every skill it was offered and whether it loaded it, the tools it called, and the files it changed. Each session on a feature's AI Usage tab links to its record. Runs from before this release are filled in from what Repave had kept, marked Backfilled.

Documents. An administrator defines the documents every project must produce under Documents in the Admin portal, with an optional .docx or .pdf template; a project can add its own on its Documents page. Repave writes each one from what it knows about the project, in your template, and exports it to Word, PDF or Markdown.

Email digest. One short email: what is waiting on you, what is waiting on teammates, which features moved, and which have gone quiet, each with a link to the exact place to act. Administrators can add a row per project across the installation.

VS Code on your computer (Experimental). Open a feature in VS Code on your own computer, in a dev container with everything Repave's own IDE has. A project editor turns it on per project in Project Settings → General; it is off in every project until then.

Delivery Metrics on the Costs page. Iterations per feature, rules in place, cost per completed feature and cost by phase, week by week. All Features gains prototype and implementation iteration columns, and Download Excel gains sheets for each.

The Mapping tab. Next to As-Is and To-Be on a feature's scenarios, Mapping shows each as-is scenario beside the to-be scenarios that trace to it, filtered by Mapped, Unmapped, Not required, Broken links and New.

Search pages from the top bar. The search box now finds pages as well as features, and ⌘K on a Mac or Ctrl+K on Windows and Linux opens it from anywhere in the project.

Filter To-Be scenarios by approval.

Improvements​

Merges on different features no longer wait for each other. While one feature's merge runs its conflict resolution and tests, merges, pull request refreshes and syncs on other features of the same project go ahead instead of failing after a minute's wait.

Agents check their work against other features in progress before the merge, so a clash with another feature's change is found and fixed by the agent, not at merge time.

"Implement with Behavior Tests" and "Implement without Behavior Tests". The verification choice in the Implement dialog has plainer names, and without is listed first and chosen by default where the project allows it. A choice you made before is kept.

Agent chat says who answered. Your answer to an agent's question appears as your own message on the right, at the time you gave it, and an answer, approval or message from someone else carries their name. Answers to pre-implementation, clarification and verification questions also show who gave them.

Desktop notifications go to the people who can answer. When an agent waits for input, the browser pops up for whoever started the run and the feature's owner; everyone else still sees it in the bell.

Gemini and Codex runs use their model's whole context window, instead of compacting at the 200K a Claude model would have. A Gemini or Codex run the gateway refuses once is resumed instead of failing.

Interactive agents on Vertex-routed projects run in auto mode on the models that support it, instead of running every action without a safety check.

Storybook prototypes. A To-Be scenario with a story opens it with Story on its card; the story preview fills the whole tab; and Adjust and Accessibility open one at a time.

Skills lists the project's own skills first, apart from Repave's. Operations in the project sidebar is now part of Management.

Agent sandboxes, Repave IDE sessions and prototype environments start about 15 seconds faster.

Screens look and behave more consistently: loading, empty and error states, buttons and page headers are the same everywhere, and links are easier to read.

Fixes​

Saving one To-Be scenario cleared every approval on the feature. Editing, moving or syncing scenarios now withdraws approval only from the scenarios that changed.

The resume dialog called a Sonnet or Opus session nearly full when it had most of its room left. It now measures the session against the 1M window it ran with.

Out of memory meters overstated how many processes were killed, by two to five times. They now count killed processes, and say Hit its memory limit when a limit was hit but nothing was killed.

A feature page could fail to open with "This page couldn't load" when one of its sessions had no recorded usage.

Agent transcripts older than a month were deleted. They are now kept.

Two Repave installations on one Docker host deleted each other's caches and sandboxes at startup. Each now removes only its own.

Opening Repave IDE on a feature could stop the session it was opening when a previous merge had left the feature's folder behind.