Armada 1.0.0

The app went from nothing to a working menu bar app between 2026-09-11 and 2026-09-13. Entries below are grouped by what they do rather than replayed commit by commit.

Added

• Sessions, per account. Every live Claude Code session with its title, project, age and state, read from each config folder's registry and transcripts. Sortable by what needs you and groupable by project, with a context total per group.

• State read rather than inferred. Claude Code's registry carries status (busy / waiting / idle) and names what a waiting session wants in waitingFor. The older write-recency and unanswered-tool_use inference survives only as the fallback for a folder on a build older than 2.1.269.

• Context occupancy. How full a session's window is, where it started, the rate it has grown at, a projection, and the last compaction — for both vendors, through one renderer so the two panes cannot drift.

• The prefix breakdown behind /context. get_context_usage, asked of a spawned claude. It describes a comparable session rather than the watched one, and the pane says so.

• Usage, per account. The 5-hour and 7-day windows with reset times, asked live through the get_usage control request and falling back to the cache on disk, with a badge naming which answered and how old it is. Day-weighted pace forecasting, a Usage overview pane, and usage history recorded to disk.

• Codex, as a spike. A second sidebar section with its own sessions, plan limits and context, read from ~/.codex — liveness from the writer locks, limits from token_count events in session logs, and a card in the global Usage pane beside the Claude accounts.

• Focus. A session row brings forward the application hosting it, resolved by walking the process tree, and raises that session's own window where Accessibility allows.

• New sessions. The detail pane with nothing selected is an account overview — the folders that account ran in last, a folder picker, and a tally of what its sessions are doing. Starting one opens a terminal running claude or codex in that folder on that account: Armada writes a startup script and hands it to Terminal, never owns the process, and the new session arrives through the watchers like any other.

• Fork a session. A copy of the session you are looking at, opened from where it stands, on the same account and in the same folder — from the detail pane, a row's right-click, or the menu bar popover. It is each vendor's own flag doing the work (--resume … --fork-session for Claude Code, codex fork for Codex), which is what makes it safe to offer for a session that is still running: forking mints a new id and leaves the original alone, where resuming would put two writers on one transcript. Claude Code records nothing linking the copy to its original and the pane says so; Codex writes forked_from_id into the new session's log.

• Mouse bindings. Middle and extra mouse buttons can cycle the session list or send a keystroke, through a CGEventTap whose mask is two event types wide.

• Menu bar. An accessory app with a per-account popover, and a template glyph that fills while anything is working and rings when a session wants attention, on a configurable ladder. Star one plan limit, in Usage or above an account's sessions, and its percentage sits beside the glyph in small type.

• Settings on swift-support-kit's shared scaffold, with About and Help panes.

• What's New, a Settings pane generated from this file, with a dot in the menu bar popover while a release is unread.

• Updates, off until you say otherwise. Sparkle reads one file, armada.mgcrea.io/appcast.xml, only once automatic checks are on or Check Now is pressed, and sends no identifier with it. A one-time card in the main window asks.

• A licence, and a 30-minute trial. One key covers every 1.x release on every Mac you own and is verified offline, on the Mac. Without one Armada watches nothing and says so where the sessions would be; the trial runs everything, and is started by hand.

• A supervisor for the fleet, off until you turn it on. Settings ▸ Supervisor runs a read-only MCP server on 127.0.0.1 and starts a Claude Code session with it attached, so you can ask one session which of the others need you, what any of them is doing or last said, and how much plan is left. Five tools, none of which can change a session, start one or write anywhere. The session runs on your own plan, and its connection details never touch your Claude configuration.

• A network claim you can check. Armada reaches no network on its own apart from the opt-in update check, and listens on one socket, the supervisor's MCP endpoint, on 127.0.0.1 only. SECURITY.md says so, and make audit asserts it against the built app.