█████╗ ██████╗ ███╗ ███╗ █████╗ ██████╗ █████╗
██╔══██╗██╔══██╗████╗ ████║██╔══██╗██╔══██╗██╔══██╗
███████║██████╔╝██╔████╔██║███████║██║ ██║███████║
██╔══██║██╔══██╗██║╚██╔╝██║██╔══██║██║ ██║██╔══██║
██║ ██║██║ ██║██║ ╚═╝ ██║██║ ██║██████╔╝██║ ██║
╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝
Persistent sessions and live supervision for coding agents.
What is Armada?
Armada runs coding agents in persistent tmux sessions and lets you monitor and control them from a dashboard or CLI.
Each agent runs in its own session and maintains state across reconnects, restarts, and devices. You can start agents from your laptop, disconnect and reconnect later, monitor execution in real time, and manage multiple agents at once.
Key Features
- Persistent agent sessions — every agent runs inside a tmux session and survives disconnects. No custom runtime.
- Live status tracking — see which agents are active, idle, pending, or error in real time.
- Web + terminal control — manage agents via the dashboard or
armada watch. - Multi-agent workflows — spawn workers and coordinate execution across a tree of agents.
- Message system — structured communication between nodes with event-driven delivery.
- MCP integration — agents interact with Armada through typed MCP tools instead of raw API calls.
Installation
Prerequisites: Python 3.10+, tmux, and either OpenCode or Claude Code installed on your PATH.
pip install armada-ai
armada setup # install agent skills for OpenCode and Claude Code
armada is now available. You can also install from source or run via Docker — see below.
Docker
docker build -t armada .
docker run -d -p 9100:9100 --name armada armada
From source
git clone https://github.com/rguiu/armada.git
cd armada
bash install.sh
Test PyPI (pre-release)
Test PyPI may contain typosquat packages that hijack dependency names. Install in two steps to keep dependencies on real PyPI:
pip install --index-url https://pypi.org/simple/ fastapi uvicorn websockets qrcode mcp 'tomli>=1.0'
pip install --index-url https://test.pypi.org/simple/ --no-deps armada-ai
armada setup
Quick Start
armada # start server + open dashboard
Open http://127.0.0.1:9100.
- Register a project — sidebar Projects → + Add. Give it an ID, name, and directory path.
- Create a node — click + Node, pick a project, choose an agent type (OpenCode, Claude Code, or Bash), optionally add an initial prompt.
- Attach — select the node and click Attach. Opens the agent session in iTerm2 (macOS) for full TUI, or xterm.js in-browser.
- Monitor — the dashboard updates every 10 seconds. See status, activity logs, and task history.
- Connect other devices — scan the QR code in the sidebar to open the dashboard on your phone or tablet.
CLI Watch Dashboard
armada watch is a live terminal dashboard for managing agents without a browser:
$ armada watch
Nodes Projects | 3 active 1 pending 12 idle | 23 agents
● HOOK20 ▣ idle PGLease unknown needs external_directory
○ HOOK18 idle PGLease server restarted — reconnected
○ H1 idle Armada
○ Armada-006 idle Armada
● Armada-005 active Armada running bash
⚠ Pending: HOOK20
┃ [↑↓]nav [enter]attach [n]ew [k]kill [d]delete [tab]projects [q]quit ┃
Full keybindings and forms
| Key | Action |
|---|---|
↑ ↓ |
Navigate agent list |
Enter |
Attach to selected node (focuses existing pane) |
a |
Split-attach (experimental — opens a new tmux pane for the node) |
n |
New node (interactive form) |
k |
Kill selected node |
d |
Delete selected node |
Tab |
Switch to Projects view |
q |
Quit |
Note:
a(split-attach) is experimental and may not work reliably in all terminal environments. It is not shown in the bottom bar but remains available as a hidden shortcut.
Forms for creating nodes and projects use keyboard navigation: Tab/↑↓ to move between fields, ←→ to cycle options, type freely in text fields, Enter on [Save] to submit, Esc to cancel.
Agent Types: Claude Code vs OpenCode
Armada supports both Claude Code and OpenCode as first-class agents. Each integrates differently:
OpenCode
OpenCode is an open-source AI coding agent. Armada's OpenCode integration uses:
- MCP Server — an Armada MCP server provides typed tools (
spawn_node,send_message,report_status, etc.) directly in the agent's tool palette. Auto-configured viaopencode.json. - Plugin system — an
armada-pendingplugin hooks into OpenCode's event loop (tool start/stop, permission requests). Agents automatically report status to Armada. - Skills —
armada-nodeandarmada-workerskill files teach agents orchestration and messaging patterns.
To use OpenCode: install it, make sure opencode is on your PATH, and run armada setup. When creating a node, select "opencode" as the agent type.
Claude Code
Claude Code is Anthropic's official CLI agent. Armada's Claude Code integration uses:
- Hook system — four shell hooks fire on tool use, idle transitions, and permission requests. These use the
armada reportCLI to report status. - Skills — the same skill files are installed to
~/.claude/skills/and auto-activate whenARMADA_NODE_NAMEis set.
To use Claude Code: install it via npm install -g @anthropic-ai/claude-code, make sure claude is on your PATH, and run armada setup. When creating a node, select "claude" as the agent type.
Bash
Bare shell nodes without an agent. Useful for running scripts or manual commands. Armada provides a bash wrapper (armada-bash.sh) with functions like armada_report_active, armada_spawn, and armada_kill_child. Status reporting uses the armada report CLI.
Which one should you use?
| OpenCode | Claude Code | |
|---|---|---|
| Install | pip install opencode |
npm install -g @anthropic-ai/claude-code |
| Status reporting | Plugin (TypeScript, event-driven) | Shell hooks (pre/post-tool, stop) |
| Permissions | Permission events in plugin | claude-permission.sh hook |
| Cost tracking | Token usage from step-finish events | Not built in |
| Best for | Open-source workflows, custom plugins | Anthropic ecosystem, official support |
Either works. Pick based on which agent you already have installed.
Commands
| Command | Description |
|---|---|
armada |
Start daemon + open dashboard |
armada --no-browser |
Start server without opening browser |
armada start |
Start daemon in background |
armada stop |
Stop the daemon |
armada watch |
Interactive terminal dashboard (htop-style) |
armada create -p <project> |
Create a new agent node |
armada nodes |
List all agents in a table |
armada attach <name> |
Attach to a node by name (iTerm2) |
armada projects |
List projects |
armada projects add <id> <name> <path> |
Register a project |
armada projects rm <id> |
Remove a project |
armada setup |
Install skills and MCP config to user profile |
armada version |
Print the Armada version |
armada token |
Print the auth token |
armada token --qr |
Print token as scannable QR code |
armada config |
Show or set configuration |
armada config set <key> <val> |
Change a config value (default_agent, port, etc.) |
armada service install |
Install as system service (launchd/systemd) |
armada status |
Show server health and agent counts |
armada doctor |
Clean up stale tmux sessions and DB state |
armada mcp |
Start the Armada MCP server (stdio mode, for AI agents) |
armada report <status> <msg> |
Report node status (used by hooks and scripts) |
armada --lan |
Bind server to LAN IP (access from other devices) |
Agent Delegation
Agents can delegate work to child nodes using MCP tools:
Orchestrator
├── Reviewer — reviews the code
└── Tests — writes and runs tests
└── sends "job completed" message back to Orchestrator
- Start Armada:
armada - Register a project and create an orchestrator node (agent type: "opencode" or "claude")
- The orchestrator uses
spawn_node("reviewer")andsend_task(node_id, "review the auth module")— agent type and project are inherited automatically - Workers send completion messages back to the parent via
send_message(to_node_id=parent_id, payload="job completed", msg_type="result") - The orchestrator collects results via
read_inbox()and cleans up withkill_node()
Skills (armada-node, armada-worker, armada-orchestrator) teach agents the full workflow including messaging patterns.
MCP Server
Armada includes an MCP (Model Context Protocol) server that exposes all operations as typed tools for AI agents. Instead of constructing curl commands, agents call tools with automatic defaults:
| Tool | Purpose |
|---|---|
spawn_node(name) |
Spawn a child node (inherits agent_type, project, parent) |
send_task(node_id, command) |
Send command to node (auto-waits for tmux init) |
kill_node(node_id) |
Kill node and descendants |
get_tree() |
Full node hierarchy with status |
get_node(node_id) |
Node details and reports |
report_status(status, message) |
Report own status |
send_message(to_node_id, payload) |
Send message to another node |
read_inbox() |
Read pending messages |
broadcast(payload) |
Send message to all children |
post_to_queue(payload) |
Post task to shared work queue |
claim_from_queue() |
Claim next available queue task |
The MCP server is auto-configured when nodes are created. Run manually with armada mcp.
Inter-Node Messaging
Nodes communicate through a task mailbox system with event-driven delivery:
- Direct messages — any node can send structured messages to any other node
- Broadcast — fan-out a message to all children with one call
- Work queue — post tasks to a shared queue for any idle agent to claim
- Event-driven delivery — no polling; the server pushes messages via tmux when the recipient goes idle
- ACK — messages track
pending → delivered → donelifecycle - Completion notifications — workers automatically notify their parent when a task is done
Architecture
Armada uses a FastAPI server with SQLite (WAL). Each node is backed by a tmux session — no custom agent runtime, just tmux providing persistence, reconnection, and multiplexing. Nodes report status via POST /api/report. The dashboard refreshes over a persistent WebSocket.
API Endpoints
| Method | Path | Purpose |
|---|---|---|
GET |
/api/tree |
Full node hierarchy |
POST |
/api/nodes |
Create node |
GET |
/api/nodes/:id |
Node detail + reports |
DELETE |
/api/nodes/:id |
Kill node + cascades to children |
POST |
/api/nodes/:id/send |
Send command to worker |
POST |
/api/nodes/:id/attach |
Open terminal attached to node |
POST |
/api/report |
Agent status report (active/idle/pending/error) |
POST |
/api/nodes/:id/messages |
Send message to node |
GET |
/api/nodes/:id/messages |
Read node inbox |
PATCH |
/api/messages/:id |
Acknowledge message (mark done) |
POST |
/api/nodes/:id/broadcast |
Broadcast to all children |
POST |
/api/queue |
Post task to shared work queue |
GET |
/api/queue |
List unclaimed queue tasks |
POST |
/api/queue/:id/claim |
Claim a queue task |
GET/POST/DELETE |
/api/project-labels |
CRUD project directories |
GET |
/health |
Health check (no auth) |
GET |
/metrics |
Prometheus metrics |
Full API docs at http://127.0.0.1:9100/docs (FastAPI Swagger UI).
Development
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[test]"
pytest # run tests
pytest --cov=armada_ai # with coverage
ruff check armada_ai/ tests/ # lint
CI runs ruff + pytest-cov on Python 3.10–3.13 on push to main.
License
MIT
Metadata
Release files for armada-ai 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| armada_ai-0.3.5.tar.gz | 204.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| armada_ai-0.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 385.8 kB
Release files / armada_ai-0.3.5.tar.gz
| Download URL | armada_ai-0.3.5.tar.gz |
|---|---|
| Size | 204.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3f4c87f2e9d4a05717fec0dd77439f4ba7979b16bf6953ba0bee9a8f4c493d1
|
|
BLAKE2b-256 checksum How to use checksums |
712a002d535cdd60e825aff84926c15d9e23b0e362820abfd6641a9a4d2fdb67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logRelease files / armada_ai-0.3.5-py3-none-any.whl
| Download URL | armada_ai-0.3.5-py3-none-any.whl |
|---|---|
| Size | 181.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8eb43ec2c12ce6c7a4278f4d6902361d60400cbfdb1620d2e331656ad1fc7485
|
|
BLAKE2b-256 checksum How to use checksums |
b2b2b08d28afaf95709cc9a7015cf91e7df6a7777c1a1f261ef6e1fa85ab2571
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logSecurity for armada-ai 0.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for armada_ai-0.3.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.