Skip to main content

Release 0.1.153

Agent questions and requests now reach you in Slack, testers can report issues straight from your staging site, and every bug report gets a ticket in your issue tracker, kept current both ways. You can install Claude Code plugins for agents and developers, and run the legacy app yourself in the browser and in the Repave IDE.

Upgrade notes​

  • Eleven database migrations run on upgrade. They only add new data; nothing existing is changed.
  • No changes to .env or docker-compose.yml.
  • New installs let Docker create about a thousand networks instead of about thirty. On a server already installed, see "Jobs fail with all predefined address pools have been fully subnetted" in the installation guide's troubleshooting to apply it.
  • To use Slack, the server needs outbound HTTPS to slack.com and *.slack.com.

New​

Slack. Under Admin portal → Slack, connect your server's own Slack app with Copy manifest and two tokens. Agent questions are posted in Slack and your answer there answers the run. Mention @Repave or send it a direct message to ask about a project or ask for a change.

Report issues from your staging site. The Repave QA extension for Chrome and Edge, hosted by your Repave server, lets testers turn on Pick issues, click what is wrong and send them as one bug report. Bug Reports shows the build each report was Seen on, and On staging — retest once staging runs the fix. IT setup on Bug Reports gives your IT admin the browser policies.

Bug reports in your issue tracker. With Jira or GitHub Issues set up, every bug report gets a ticket. The investigation's findings are added as a comment, and status moves both ways: a fix closes the ticket, and closing the ticket resolves the report. Comment /repave investigate or /repave fix … on any ticket to start a run from the tracker.

Pull requests for bug fixes. In pull-request merge mode, a bug fix with no unmerged branch to land on stays on its own branch, and Create pull request on Fix Result opens a pull request for it.

Plugins. Plugins under Management, and Admin → Plugins for every project, add Claude Code marketplaces from git, a hosted file or a zip, and install plugins for your agents, your developers in the Repave IDE, or both. Plugins can update automatically; administrators can limit sources and block plugins.

Run the legacy app yourself. Run app on Tools → Legacy App starts your own copy of the legacy Windows app, live in the page: click, type and drag as on a Windows PC. The project assistant uses the same copy and shows it in its panel. In the Repave IDE, Repave: Open Legacy App opens the app beside Claude Code and Codex.

The Domain page. Writing the To-Be now builds a domain model of the new application: its subdomains and aggregates, on a new Domain page under Design & Architecture, as a list or a diagram. Each scenario names the aggregates it uses, and new API endpoints follow the model. You can edit, rename, move and merge entries, and Download CML for Context Mapper.

Serious code review findings come to you. When a security hole or data loss is still in the code after the review rounds, the run asks you Fix it or Don't fix it. A fix counts only once the review checks it again. The code review now always runs on the Implementation agent's model.

Tag someone on an agent question. Tag someone on a question card asks another editor of the project to help, with an optional note; they are notified in Repave, Slack and the daily email.

Screenshots in documents. Ask for screenshots in a document's brief, or use a template with pictures of screens, and the document shows the new app's screens.

/repave:scenario in the Repave IDE adds, changes, renames, removes or rewrites a feature's To-Be scenarios.

Improvements​

  • The top-bar search finds pages despite typos, initials (pr) and short forms (stgbr), listed after exact matches.
  • When Docker runs out of room for networks, Repave first removes its own leftover networks.
  • A test upload that renamed a scenario is refused, naming the old and new titles: rename it with /repave:scenario, then upload again.

Fixes​

  • A module run stopped by two contradicting hard rules failed without saying why. It now lists the rules with Review, and Retry waits until the conflict is resolved.
  • After a failed module run, members fixed in the Repave IDE and verified were not counted, so the next step stayed hidden.
  • A resumed run could repeat old replies or re-run unit tests that had already passed.
  • After a Repave restart, a resumed job could lose its features, and a unit-test run it interrupted was marked failed instead of run again.
  • Continue after you approved a scenario removal refused instead of implementing the rest.
  • A pull request's fix round could restart when only new commits from the base branch were merged in.