VitalAIze 0.4.0

VitalAIze 0.4.0 shows what shipped work costs: what the agent sessions behind each merged pull request spent, the CI minutes each session's pushes caused, and an alert when a day or week goes over the budget you set.

What is new

• Cost per merged pull request. A Shipped section on Trends shows merged pull requests per day, Claude's cost per merged pull request, sessions per merged pull request, and tokens per merged pull request with Claude and Codex added together. When you use both tools, the Claude and Codex comparison now leads with tokens per merged pull request, in place of tokens per 1,000 lines.
• CI minutes per session and per pull request, counted the way GitHub bills them: each job rounded up to a whole minute, and a Windows minute counted as 2 and a macOS minute as 10. A session's details show the minutes its pushes caused, and Trends adds them up.
• Budget limits. Set a limit on Claude spend, Claude tokens or Codex tokens, per day or per week, under Budget in Settings. When a total passes its limit, a strip on the board says so and one alert goes out, on the channels you pick.
• Your own CI machines. If some of your GitHub Actions jobs run on your own machines (self-hosted runners), the Git tab says which runs they worked on and whether each runner is up, and Trends splits runner time between GitHub's machines and yours. VitalAIze only reads: it never installs, starts or changes a runner.
• Tap a run on the Git tab to see its details over the board: each job, the runner it ran on, the step that failed, and a link to GitHub.
• Type the New Relic key in, in the Mac app or vitalaize setup, instead of only pointing at 1Password. It is kept in your login keychain on a Mac and in a file only you can read on Linux, never in the settings file.
• 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 (14 days) back.

Install

• Mac (Apple silicon): download VitalAIze-0.4.0.pkg below and open it. It is signed and notarized by Apple.
• Linux: download vitalaize-0.4.0-linux-x86_64.tar.gz (Intel and AMD) or vitalaize-0.4.0-linux-arm64.tar.gz (ARM), unpack it, and run bin/vitalaize setup.

The README has every step.

Upgrading from 0.3.0

• Install 0.4.0 the same way you installed 0.3.0, on the hub and on each collector. Pairings and settings are kept.
• A collector still on 0.3.0 keeps working with a 0.4.0 hub. Only a 0.4.0 collector reports the GitHub runners on its machine, and finds out when it was removed while it was off.
• Budget limits need the archive, which is on unless you turned it off.
• If you still run 0.2.0, the 0.3.0 notes say how to move each machine across. On Linux, upgrade now: every copy of the 0.2.0 download had the same built-in secret for remote control.

Known limits

• CI minutes are an estimate of GitHub's bill. GitHub prices its larger runners by size, which the board cannot see, so they count as a standard runner would. Minutes inside your plan's allowance are counted too.
• A session on a long-lived branch such as develop collects everyone's runs on that branch while it works there.
• Still not tried by us between two real machines on a network, and Codex "Needs you" not yet with a real Codex.
• Keep the hub on a network you trust. The link from a collector is encrypted, but the board itself is plain http.

The full list is on Known limits. Report problems in Issues and ask questions in Q&A.