Skip to main content

Release 0.1.148

Stopping a module's implementation now keeps the features it finished, and code review also folds new code that repeats what your codebase already has. Repave IDE sessions on a module ask which feature you mean, and desktop notifications reach only the people a job concerns.

Upgrade notes​

  • A database migration runs automatically during the upgrade. It records who last restarted, continued or resumed a job.
  • No changes to .env or docker-compose.yml.

New​

Code review finds duplicates. Besides bugs, the review now looks for new code that does the same job as code your codebase already has, and the agent folds it into the existing code without changing what that code's other callers get. A duplicate still there when the review rounds run out is listed with the implementation warnings, marked Duplicate.

Repave IDE knows the module you are working on. In a session on a module's branch, the agent asks which of the module's features a command is for before it changes anything, and works only on that module's features.

The Modules page has search and pages. Search with Search modules..., page through it like the features list, and going Back from a module returns to the same search, sort and page. The Verified column now reads Tests written.

Improvements​

A module's implementation keeps what it finished. Each feature is marked implemented as soon as its turn passes its checks, so the Implemented count goes up as the run goes. Stopping the run, or a Repave restart, leaves those features implemented, and Implement module then ticks only the ones left. While the module is being implemented, Write Tests for one of its features waits.

Desktop notifications go to the job's people. A job finishing, failing or timing out, a design ready for review and the design agent's questions pop up only for whoever started, restarted, continued or resumed the job, and the feature's owner. Everyone still sees them in the notification bell.

Scenario questions are answered Yes or No. A Yes writes the scenario exactly as shown; only a No takes a detail, which the agent reads and may ask again with.

  • The Running agents button glows amber while an agent is waiting for you.
  • A running module's status names its stage without a count, such as Implementing; while a module's tests are being written it reads Writing tests.
  • Before asking you about a To-Be scenario, agents read the As-Is scenarios and legacy code it came from, and ask only when those do not answer it.

Fixes​

  • Answering a fix round's question in your own words, or with Fix it, reached the agent as if you had declined without being asked.
  • Continuing a stopped fixing run could redo features it had already finished.
  • Questions an agent asked after starting background work, such as a server, came back "interrupted" and were lost.
  • A failing frontend (Vitest) test suite stopped with "Unit tests could not finish" instead of being fixed.
  • After moving a feature's work onto its module's branch, the feature's header showed the old branch until you reloaded.