VitalAIze 0.4.1

VitalAIze 0.4.1 fixes one thing: installing a new version over a running board now restarts it.

What is fixed

• The board restarts when you install over it. Before, the board kept running the old version after an install, with its files replaced, so it showed bare text without its style sheet, scripts or icons until it was restarted. Only the VitalAIze app restarted it, and the app does not open after an install from the command line (sudo installer -pkg ...), or when nobody is at the screen. Now the installer itself restarts a board or collector that is running, for each person on the Mac, and leaves one that was stopped as it was. (#141)

Install

• Mac (Apple silicon): download VitalAIze-0.4.1.pkg and open it. It is signed and notarized by Apple.
• Linux: download vitalaize-0.4.1-linux-x86_64.tar.gz (Intel and AMD) or vitalaize-0.4.1-linux-arm64.tar.gz (ARM), unpack it, and run bin/vitalaize setup. The fix is in the Mac installer only; the Linux downloads are the same as 0.4.0 apart from the version number and the README.

The README has every step.

Upgrading from 0.4.0

Install 0.4.1 the same way, over 0.4.0. Nothing else changes: your settings and database stay as they are, and a 0.4.0 collector keeps working with a 0.4.1 hub.

What 0.4.0 added is in the 0.4.0 release notes. What VitalAIze does not do yet is on Known limits.

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.

VitalAIze 0.3.0

VitalAIze 0.3.0 puts your other machines on the board, live. Each one runs a small collector that streams its Claude Code and Codex sessions to the hub over an encrypted link, and you connect it with a six-digit code.

What is new

• Your other machines, live. A collector on each machine watches its own sessions and streams them to the hub. Their sessions get cards as they work, show Needs you, and send your alerts. It sends numbers and a few short lines (a session's title, its folder and branch, and the start of your prompts). It never sends the agent's replies, the commands it ran or your files. The wiki lists what crosses the network.
• Connect a machine by code. The new machine shows a six-digit code, and you approve the same code on the hub's board. There is no key to copy. At most you type the hub's address.
• A mailbox on the board. The envelope by the clock holds the few things the board needs you to decide: a machine that wants to connect, and whether to track a repository someone started working in.
• Settings in the Mac app, or vitalaize setup in a terminal. Most changes are in use within seconds, with no restart.
• Tabs and several repositories. The board has an Agents tab and a Git tab. Follow up to about six repositories: the status line adds them up, and each one shows its own workflow runs.
• Alerts anywhere. Slack, ntfy (iPhone or Android) and Pushover, besides Messages on a Mac, so a Linux hub can alert you too.
• Codex. Codex sessions on your other machines reach the board, and a Codex session can show Needs you after a one-time step (Codex).
• A note when a new version is out, which you can turn off.

Install

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

The README has every step. To try the collector step by step, follow the test guide.

Upgrading from 0.2.0

• Install 0.3.0 the same way you installed 0.2.0. On a Mac, opening the new app mends what an older install left behind and says what it did.
• A machine you connected with 0.2.0's Connect command stops sending until you install 0.3.0 on it as a collector. Setup takes the old upload hooks out for you and leaves your other hooks alone.
• If you run 0.2.0 on Linux, upgrade. Every copy of that download had the same built-in secret for remote control. 0.3.0 turns remote control off.

Known limits

• Tested on one Mac and in automated tests on Linux and macOS. We have not yet run the collector between two real machines on a network ourselves. Please tell us what you find.
• Codex "Needs you" has not yet been seen working with a real Codex. It may mark a card wrongly.
• New Relic: the key can only come from 1Password, and the checks are set in settings.exs only. A field to type the key in is planned for 0.3.1.
• A machine you disconnect while it is off never learns it. It keeps trying and says the hub is not answering. Pair it again.
• 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.

VitalAIze 0.2.0: Linux

VitalAIze now runs on Linux.

Mac (Apple silicon): download VitalAIze-0.2.0.pkg and open it. It is signed and notarized by Apple, and walks you through setup.

Linux: download vitalaize-0.2.0-linux-x86_64.tar.gz (Intel and AMD) or vitalaize-0.2.0-linux-arm64.tar.gz (ARM). It carries everything it runs on and works on Ubuntu 22.04, Debian 12 and newer. Unpack it, copy settings.example.exs to settings.exs and fill it in, then run ./systemd.sh on to start the board and keep it running. See "Install on Linux" in the README.

What's new:

• Linux downloads for Intel and ARM, with a systemd service to start the board at login.
• 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 now works there (it needs python3 and curl).
• On Linux the database lives in ~/.local/share/vitalaize.

Text alerts still need a Mac, since they go through Messages.

VitalAIze 0.1.0

The first release of Kyroco VitalAIze: a wall screen for teams building with Claude Code and Codex.

Install on a Mac (Apple silicon): download VitalAIze-0.1.0.pkg below and open it. It is signed and notarized by Apple. When it finishes, VitalAIze opens and asks what this Mac does (hub, collector or both), fills in what it can find, and starts the board.

What's in it:

• 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 vs 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.

Building from source, and running on Linux, are covered in the README.