Status

What each release shipped, and what is being built now. This page matches our tracker as of October 6, 2026. Downloads are on the releases page. For what comes after, see the Roadmap.

Being built now

Step 3 of the Roadmap, which will be 0.5.0: keep agents moving.

0.4.1: a fix for upgrades (October 6, 2026)

The latest release. To install it or to upgrade, follow the README; what it does not do yet is on Known limits.

• The board restarts when you install over it. Installing a new version over a running board used to leave the old version running with its files replaced, so it showed bare text until it was restarted. The installer now restarts a running board or collector itself, also on an install from the command line.

0.4.0: what shipped work costs (October 6, 2026)

Step 2 of the Roadmap.

• Cost per merged pull request. A Shipped section on Trends: merged pull requests, Claude's cost per merged pull request, and tokens per merged pull request. Tokens per merged pull request leads the Claude and Codex comparison, in place of tokens per 1,000 lines.
• CI minutes per session and per pull request, counted the way GitHub bills them, in a session's details and on Trends.
• Budget limits. A limit on Claude spend, Claude tokens or Codex tokens, per day or per week. Passing one shows a strip on the board and sends one alert. See Alerts.
• Your own CI machines. The Git tab shows which runs ran on your own machines (self-hosted runners) and whether each runner is up, and Trends splits runner time between GitHub's machines and yours.
• Tap a run on the Git tab to see its jobs, runners and the step that failed in a panel over the board.
• Type the New Relic key in, in the Mac app or vitalaize setup, instead of only pointing at 1Password.
• A collector removed while it was off finds out when it comes back, and stops trying.
• GitHub runs from the days the board was off are saved when it comes back, up to archive.backfill_days back.
• Fixed before the release: each merged pull request counts once; a GitHub read that hangs is stopped instead of freezing the board's numbers for a day; the hub keeps out numbers from a collector that cannot be right; a run waiting for approval says so; Remove says what happened to the New Relic key.

The work toward forecasts of where your plan limits will land moved out of this release; it has no version yet.

0.3.0: your other machines, live (October 1, 2026)

It was step 1 of the Roadmap and holds two groups of changes.

Close the gaps from 0.2.0

• Several repositories. Follow up to about six at once. The status line adds them up, and the Git tab gives the four busiest a column each and lists the rest below.
• Alerts anywhere. Slack, ntfy (iPhone or Android) and Pushover, besides Messages on a Mac, so a Linux hub can alert you too.
• Codex needing you. Codex sessions can show Needs you, through a small Codex hook. This is new and not yet tried with a real Codex; see Known limits.
• A note when a new version is out, which you can turn off.
• Checked on every change. Each pull request runs the tests, a code style check and a compiler warning check on Linux and macOS, a security scan of the code (Sobelow), and a check of the libraries VitalAIze uses for known security holes. Those libraries are updated weekly. Each release builds its Linux downloads on real Intel and ARM machines and checks that each one starts.
• A safety fix for 0.2.0 on Linux. Every copy of the 0.2.0 Linux download had the same built-in secret for remote control, so a board started by hand (not with systemd.sh) let anyone on your network who also had the download run commands on your machine. 0.3.0 turns remote control off unless you ask for it by setting RELEASE_DISTRIBUTION; if you do, also set RELEASE_COOKIE to a secret of your own.
• This wiki.

The streaming collector

A new way to connect your other machines, which replaces the Connect command, the upload scripts and the shared key of 0.2.0. See How it works.

• What a collector may send: the messages, and one filter that decides what crosses the network.
• An encrypted link between a collector and the hub, with a certificate for each machine and calm reconnects.
• Collector mode: a small, always-running collector that watches its own machine.
• Pairing by code, the mailbox on the board, and the connected machines list.
• Other machines' sessions, live on the hub's board and saved in its archive.
• The mailbox asks to track a repository when a machine works in one the Git tab does not follow.
• Settings in the Mac app and in vitalaize setup in a terminal, which restart only what changed.
• The upload scripts and the shared key are gone, and setup moves a machine connected the old way across.
• The README, this wiki and a test guide for the new collector.

Fixed before the release

• Each repository on the Git tab shows its own workflow runs. A second repository whose workflow files had other names showed an empty chart and "Main Unknown". A repository can now name its own gate, dev and prod workflows, and one with no gate gets Main from its latest runs on main.
• A stopped background session is no longer shown as Working.
• Chats the Codex app copies in no longer fill the Agents tab with idle cards, and a copy of a Claude session the board already reads is not saved twice. Codex cards show the end of the session's id, which tells sessions apart.
• A machine removed in the moment it connects is told so, and stops trying.

Not fixed yet

• A machine you disconnect while it is off never learns it, and keeps trying. Fixed in 0.4.0.
• The collector has not yet been tried by us between two real machines on a network, and Codex "Needs you" not yet with a real Codex. See Known limits.

0.2.0: Linux (September 29, 2026)

• Linux downloads for Intel and ARM, with a systemd service that starts the board when you log in.
• A Linux hub announces itself on the network when avahi-utils is installed, so collectors find it by themselves.
• A Linux machine can be a collector: the Connect command on the hub's Settings page works there too (it needs python3 and curl).
• On Linux the database lives in ~/.local/share/vitalaize.

Text alerts still needed a Mac in 0.2.0, since they went through Messages.

0.1.0: the first release (September 29, 2026)

• A Mac installer, signed and notarized by Apple, that asks what the Mac does (hub, collector or both), fills in what it can find, and starts the board.
• Live cards for every Claude Code and Codex session, marked with each tool's icon: working, idle or needs you.
• GitHub Actions: what is running, recent runs, a 6-hour timeline and deploy tiles.
• An archive of every session, and Trends with a Claude and Codex comparison (tokens per 1,000 lines added, tokens, lines added, failed tool calls).
• Light and dark mode, text alerts through Messages, and an optional New Relic page.