What changed, and when.

The started and updated times on a run page no longer flash a raw timestamp before settling on "2h ago" when you refresh.

Pipemason can keep your app running in a Docker or Podman container while the agents edit your code. Turn it on with live.enabled: true in your pipeline config and give it the URL your app answers on.

When an edit breaks the running app, the agent that made the edit sees the error output right away and fixes it before moving on, instead of the break surfacing phases later.

A repo with no container setup is asked once whether pipemason may write one (a Dockerfile, a compose file and a .dockerignore); you can also set this to always or never.

pipemason doctor now reports whether Docker or Podman is installed and running.

A break report carries the file, line and plugin from the dev server's error output, not only its first line.

Settings pipemason writes into your pipeline config for you (such as remembering your answer about container setup) keep your comments and layout.

A run that created its log file after starting showed a moving phase but an empty log on the run page. Every line now reaches the dashboard no matter when the log file first appears.

The run page log is no longer a short scrolling box. It shows every line and the page itself grows to fit.

Log lines are listed newest first by default. A button at the top of the log switches to oldest first, and the choice is remembered in your browser.

The run page "updated" time now reflects the latest activity. It used to show the start time until a new event arrived.

A colored section break marks every phase change in the log, labeled with the phase name, so you can see at a glance which phase each line belongs to.

The log shows the whole run history instead of the last 50 events, so the work of every agent stays visible on long runs.

Acceptance-criteria results recorded at the same moment no longer appear twice in the log, and the newest-first / oldest-first button works again on runs that have them.

The dashboard cost figure now says whether a run was covered by your plan or billed to an API key.

Filter a program's story list by status to find in-flight, done or blocked stories quickly.

The program page shows in-flight stories as they run, rolls up acceptance criteria correctly, and lets you cancel work that has stopped.

Every story attempt in a program appears as its own run, so you can open any attempt and read its log.

Restarting a run or program supersedes the old entry instead of leaving a duplicate. Abandoned programs are labeled, and failed junk runs are cleared from the list.

Phase and status labels read as plain words, and an empty story list explains why it is empty.

Program story rows stay in sync with the roadmap file, including a final sync when the runner stops.

Log times display in your time zone instead of UTC.

Abandoned runs, per-run failure classes and cost per completed story are reported correctly. Escalations are no longer counted as failures.

Before a branch is handed back, an automated review pass reads the change, raises findings, and holds the PR until each thread is resolved. The PR carries a summary of what was reviewed.

Review verdicts appear in the run's live feed as they happen.

Each build phase ends with a check that the work still matches the plan. Drift is reported on the run page with what moved and why.

The run page shows a scorecard of each acceptance criterion with its verdict, so you can see what passed before you open the PR.

Export a run's or a program's full log from the run page or the command line.

Run and program notification emails are sent once instead of twice.

Dashboard spend and token totals include program runs, not just single runs.

Choose which run and program events send you a push notification.

Dark mode across pipemason.com and the dashboard, following your system setting with a manual toggle.

Documentation moved to its own site at docs.pipemason.com.

Push notifications for run and program state changes.

The run page updates live without a refresh.

Install the runner as a single binary with Homebrew or Scoop. No Node toolchain required.

Cancel a run or a whole program from the dashboard or the command line.