Roadmap

What we built last, what we are building now and what comes after, in the order we plan to build it. Each step is a group of changes that belong together. The plan lives in our tracker and can change; this page matches it as of October 6, 2026. To suggest something, post in Ideas.

Each step is a version: step 1 is 0.3.0, step 2 is 0.4.0, and so on. If we release before a step is finished, that release is a point release of the version before it, such as 0.3.1 or 0.3.2.

For what each release shipped, see Status.

1. Version 0.3.0: close the gaps, and the streaming collector (released October 1, 2026)

This version is out. It holds two groups of changes.

• Close the gaps from 0.2.0. Tests on every pull request, alerts on Slack, ntfy and Pushover so Linux hubs and Android phones get them, Codex sessions that can show Needs you, several repositories on the Git tab, and a note when a new version is out.
• The streaming collector. A new way to connect your other machines. Each one runs a small collector that watches its own Claude Code and Codex sessions and streams only the numbers and short status lines the board needs to the hub, over an encrypted link. You connect a machine with a six-digit code that you approve in a new mailbox on the board. It replaces the Connect command, the upload scripts and the shared key of 0.2.0. Status lists what shipped.

2. Version 0.4.0: what shipped work costs (released October 6, 2026)

This version is out. It replaces tokens per 1,000 lines with the numbers people ask for.

• Cost per merged pull request. What the agent sessions behind each merged pull request cost.
• CI minutes per session and per pull request. How much GitHub Actions time each session's work burns.
• Budget limits. A limit on Claude spend, Claude tokens or Codex tokens, per day or per week, with an alert when one is passed.
• Run details. Tap a run on the Git tab to see its details in a panel over the board.
• Self-hosted runners. Which jobs ran on your own machines, and whether each runner is up.
• Type in the New Relic key, instead of only pointing at 1Password.

Status lists what shipped.

3. Version 0.5.0: keep agents moving (next)

Turn the board from something you watch into something you act on.

• Your response time. How long agents wait on you.
• Answer from the board. Approve, deny or reply to a waiting agent from the iPad.
• Collision warning. A warning when two agents edit the same files or branch.
• Stuck sessions. Flag sessions that look stuck.
• While you were away. What agents did since you last looked.

4. Version 0.6.0: team hub and code quality

Make a shared hub useful for a team.

• Per-person view. Filter every tab by person.
• Code quality. Rework rate, and code review findings by how serious they are, beside speed.
• More coding agents. Gemini CLI and Cursor, besides Claude Code and Codex.
• Leader Board. A score that rewards good work with agents. It comes last, since it needs the per-person view, code quality, cost per merged pull request and response time first.

5. Version 0.7.0: advice from your own sessions

Use the numbers from the earlier steps to say what to change, not only what happened.

• Workflow tips. Ways to use agents better, ranked by what they would save, backed by your own sessions.
• What works best. Which skills, commands and helper agents lead to merged work cheaply.
• Korium payoff. Whether sessions that use Korium finish faster and cheaper.
• Blog tab. Agents write up their sessions in their own words, once a day.

These come last because they rest on cost per merged pull request, response time and CI minutes.

6. Version 0.8.0: components, so anyone can add a tab

Today the board's tabs are fixed: Agents, Git and New Relic. A component is a folder with a short description of a tab and a small program, in any language, that fetches the data for it. The hub finds the folder and shows it as a tab, so you can add a tool we do not support without touching VitalAIze's code.

• The hub runs a component from its folder and shows it as a tab.
• Settings for a component. Turn one on and give it its settings and secrets, in the app and in vitalaize setup.
• New Relic as the first component, taken out of the hub's own code.
• A reviewed public library of components, and a command to add one.
• A guide to writing one, with a Slack channel built from start to finish.

Also planned

These have no place in the order yet, so no version.

• Windows collector. Let a Windows machine report its Claude Code and Codex work to a hub, as Mac and Linux collectors do. Hubs stay on Mac and Linux. It comes after the streaming collector, since it is that same collector built for Windows.
• Limit forecasts. Where your Claude and Codex plan limits, and your GitHub Actions minutes, will land by the end of the month. Planned for 0.4.0, and moved out of it.
• Updates from the board. Install a new version from the mailbox, and have the board restart by itself.