Roadmap
M1 to M3 and the Board pipeline are built and merged, since the first commit on 7 October 2026. The next milestone brings Codex into the fleet. Every row links the issue that delivered it, and shipped rows carry their merge date.
- 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
- M3.7 · 2026-10-14Planner: a brief becomes graded tasks, reviewed before they reach the fleet
- M3.8 · 2026-10-14Claude Code integration: plugin hooks, MCP tools and away-mode remote approval
- M3.9 · 2026-10-14Design stage: HTML mockups from a UI profile, pinned comments, approval
- M3.10 · 2026-10-15Project Board: Nautelle-owned cards and a dedicated worker per card
- W
One sentence in, merged PR out
ShippedThe Board grows into a full pipeline: intake, design, a worker per card and cards that ship themselves.
- W.1 · 2026-10-16Planner on the Board: New work interview with question rounds and recommendations
- W.2 · 2026-10-16Intake that splits one request into cards or proposes a stack
- W.3 · 2026-10-16Cards that ship themselves: draft PR, CI watched with up to 3 fix rounds, auto-merge
- W.4 · 2026-10-16Stacks: staged cards that share one approved design
- W.5 · 2026-10-16Ready and Waiting, Auto-run, bulk actions and Discuss mode on the Board
- W.6 · 2026-10-17Steward: stuck work detected, safe fixes applied, a daily digest
- W.7 · 2026-10-17Token Saver: filtered command output, guarded reads, measured savings
- W.8 · 2026-10-17Context handoff: a short note per card so the next round starts in context
- W.9 · 2026-10-17Project coding rules, injected into every worker prompt
- W.10 · 2026-10-17Telegram Mini App, Board commands, voice and photo intake
- W.11 · 2026-10-18Assistant chat and Admin AI providers (LLM gateway with sealed keys and caps)
- 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.
- 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.