Roadmap
Three milestones are built and merged. The fourth brings Codex into the fleet. Every row links the issue and spec that delivered it.
- M1
See the fleet
ShippedOne screen for every agent, with history and cost.
- M1.1Auth, registration with approval, roles and project membership
- M1.2Hash-chained audit log
- M1.3Runner daemon, pairing, WebSocket protocol, runtime profiles
- M1.4Projects: connect by path, detect origin, config, base and docs
- M1.5Fleet observation from tmux, worktrees, boards and replies
- M1.6Agent sessions and the session tree
- M1.7Tokens and API-equivalent cost, OTel receiver in the runner
- M1.8Application shell and live updates
- M2
Steer the fleet
ShippedAct on what you see without opening a terminal.
- M2.1Structured Code Sentinel events (events.jsonl, state.json)
- M2.2Orchestrator start, stop, next and status; stop a slot; message a worker
- M2.3Read-only live pane
- M2.4Task queue from GitHub, create issue
- M2.5Merge approval queue
- M2.6Activity feed and execution history
- M2.7In-app notifications and the Telegram bot
- M3
Automate
ShippedLet the fleet run on schedules, events and limits.
- M3.1Skills: skills.sh catalog, install, headless runs
- M3.2Cron schedules with a missed-run policy, on BullMQ
- M3.3Signed inbound triggers and outbound webhooks
- M3.4Read-only GitHub App for push events
- M3.5Budgets per project or user, alert or hard stop
- M3.6Interactive terminal attach, admin only and audited
- M4
Codex in the fleet
PlannedCodex as a first-class runtime for workers and the orchestrator.
- M4.1Code Sentinel dispatches Codex workers (dispatch.sh --runtime codex)
- M4.2Codex worker fence: worktree, sandbox and a pre-merge ownership check
- M4.3Codex as the orchestrator
Known gaps
Things you might expect that are not there yet. Said plainly, so you can plan around them.
- Codex transcripts are listed but not parsed yet, so Codex sessions carry no tokens or cost.
- Overview tiles for running slots, blocked items and cost today.
- A published container image and a one-command installer.
- Approving merges from the UI needs the matching Code Sentinel release.
- Single sign-on. Accounts are local, with argon2id passwords.
- Forges other than GitHub.