Implementation BlueprintExecution layer

Armada Multi-Account Agent Fleet Setup (5-7 days)

A delivery playbook that installs Armada on a client Mac, wires every Claude Code, Codex, and Grok Build account into one menu bar dashboard, and hands over a supervisor workflow that flags blocked sessions and limit resets before they cost billable hours. Time: 5-7 days.

By InnovaAI ResearchPublished Updated

AI Code Tools

How do you implement it?

Blueprint

Armada Multi-Account Agent Fleet Setup (5-7 days)

A delivery playbook that installs Armada on a client Mac, wires every Claude Code, Codex, and Grok Build account into one menu bar dashboard, and hands over a supervisor workflow that flags blocked sessions and limit resets before they cost billable hours.

Prerequisites
  • Client runs macOS and has at least two AI coding accounts across Claude Code, Codex, or Grok Build
  • The claude, codex, or grok CLI binaries are invokable on the target machine, since Armada calls them to fetch plan limits and usage figures
  • Read access to the config folders Armada watches: ~/.claude and ~/.claude-* siblings, CLAUDE_CONFIG_DIR, ~/.codex and CODEX_HOME, ~/.grok and GROK_HOME
  • A named client-side owner who will receive the alert threshold profile and the handover documentation
  • One Armada licence purchased at $14.99 for the Mac being configured
Execution Timeline
  • 1.Install the signed, notarized Armada app on the client Mac and confirm the menu bar icon is live
  • 2.Inventory every AI coding account the client pays for and map each one to its config folder
  • 3.Verify the client's own claude, codex, or grok CLI binaries respond before Armada tries to read plan limits
  • 1.Point Armada at the Claude Code config folders (~/.claude, ~/.claude-* siblings, CLAUDE_CONFIG_DIR) and confirm each account appears as a separate entry
  • 2.Register the Codex home folders (~/.codex and CODEX_HOME) and the Grok Build home folder (~/.grok and GROK_HOME)
  • 3.Record which accounts and vendors show up in the unified session dashboard and note any that fail to register
  • 1.Walk the client through the session state view: waiting for input, running tools, idle
  • 2.Review context window occupancy and growth per session against the client's real project sizes
  • 3.Capture the 5-hour and 7-day plan limit readings with reset times and forecasts as the baseline
  • 1.Build a custom alert threshold profile matching the client's plan limits and context budgets
  • 2.Set thresholds so a session nearing its context ceiling or a plan nearing its 5-hour limit surfaces before the developer notices
  • 3.Test the profile against a deliberately loaded session to confirm the alert fires
  • 1.Stand up the read-only MCP endpoint with its seven tools so a supervisor agent can query fleet status
  • 2.Open the transcript view and confirm a supervisor agent can read session history without write access
  • 3.Demonstrate forking a session and continuing it on another account when one hits its limit
  • 1.Document the standard operating procedure for reading the dashboard at the start of each delivery block
  • 2.Train the client's lead developer on forking and account-switching so limit resets stop stalling work
  • 3.Hand over the alert threshold profile and the config folder map as written artifacts
  • 1.Run a full day of live sessions and compare actual dashboard readings against the day 3 baseline
  • 2.Adjust thresholds where the client's real usage diverged from the initial profile
  • 3.Close the engagement with a recorded walkthrough of the supervisor workflow
$1,350 to $2,400 in agency delivery time, plus $14.99 for the Armada licence covering every 1.x release and valid on every Mac the client owns or controls5-7 days
ROI Logic

The Armada licence is a one-time $14.99, so the entire fee is agency labour and margin rather than a recurring vendor cost. A 12-hour setup billed at $1,350 returns roughly $112 per hour, and the same configuration can be cloned to the next Mac-based client with only the config folder map and threshold profile changed. Because the licence covers every 1.x release and every Mac the client controls, there is no per-seat cost to absorb as the client's agent fleet grows.

Deliverables
  • Armada install with every Claude Code, Codex, and Grok Build account registered as a separate dashboard entry
  • Written config folder map covering ~/.claude, ~/.claude-* siblings, CLAUDE_CONFIG_DIR, ~/.codex, CODEX_HOME, ~/.grok, and GROK_HOME
  • Custom alert threshold profile tuned to the client's plan limits and context budgets
  • Read-only MCP endpoint configuration with its seven supervisor tools documented
  • Session handover SOP covering fork and account-switch procedure for limit resets
Definition of Done

The client's lead developer can open the Armada menu bar, name which session is blocked and which account is closest to its 5-hour limit, and fork that session onto another account without asking the agency for help.

Open the Armada courseArmada decision recordBrowse the Academy

More on Armada

More for AI Code Tools