Lakitu — Cockpit TUI para Frotas de Agentes Claude
dac2k9/lakitu
Supervisão ao vivo de múltiplos agentes Claude Code em uma tela unificada
Ver no GitHubUm servidor MCP que fornece uma interface de terminal em tempo real para orquestrar múltiplos agentes Claude Code em paralelo. Monitora presença, caixas de entrada, tarefas, personas e integra com quadros GitHub, mantendo toda a frota sincronizada através de um armazenamento compartilhado em disco.
Instalação
npx convez-ai dac2k9/lakitu1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Orquestração de múltiplos agentes Claude Code trabalhando em paralelo
- Monitoramento de presença, inboxes e progresso de agentes distribuídos
- Automação de fluxos de trabalho em GitHub com integração Projects v2
- Coordenação de tarefas e personas entre agentes em diferentes máquinas
Veredito

Lakitu é uma solução robusta para equipes que rodam múltiplos agentes Claude em produção. Exige setup em Rust e conhecimento de MCP, mas oferece supervisão centralizada e coordenação real entre agentes — essencial para workflows paralelos complexos.
README
A tradução para o português deste README ainda está na fila.
Lakitu
A live cockpit for a fleet of coordinating Claude Code agents.
When you run several Claude Code agents in parallel — across repos, even across machines — Lakitu is the screen you keep open: a TUI that shows every agent's presence, what it's working on, its inbox, its tasks, and the work flowing through your GitHub board. The agents coordinate through a small MCP server and a shared on-disk store; the cockpit renders it live.
The name is an homage: Lakitu is the cloud-riding cameraman who keeps the lens on the whole stage. That's the job — watch the fleet from above.
How it fits together
agents (Claude Code) you
┌──────────────────┐ ┌─────────────────┐
│ lakitu-mcp (MCP) │ │ lakitu (cockpit)│
│ register / │ │ live TUI over │
│ heartbeat / │────▶│ the same store │
│ messages / │ └─────────────────┘
│ tasks / personas│ ▲
└──────────────────┘ │
│ writes │ reads
▼ │
~/.claude/lakitu-fleet/ ◀───────┘ (shared store: registry, inboxes,
tasks, personas, presence)
lakitu— the cockpit TUI (the supervisor's view).lakitu-mcp— the MCP server agents talk to; also runs as an HTTP daemon (lakitu-mcp serve) so a fleet can span machines.- fleet hooks — small shell hooks wired into Claude Code's lifecycle that report presence, wake idle agents on new mail, inject personas + open tasks at session start, and feed the usage chip.
- the
fleet-coordinationskill — teaches an agent how to join the fleet.
Install
cargo install lakitu lakitu-mcp # the two binaries
lakitu-mcp install-hooks # set up the fleet hooks + skill
install-hooks writes the lifecycle hooks and the fleet-coordination skill
into ~/.claude and wires them into settings.json (backing it up first) — no
clone needed, and it's idempotent. (If you'd rather work from a clone, running
./scripts/install-fleet.sh does the same thing.)
Bring an agent online (in the repo it works in):
// .mcp.json
{ "mcpServers": { "lakitu-mcp": { "command": "lakitu-mcp" } } }
export LAKITU_FLEET_NAME=aria # a stable name for this agent
…then watch them all:
lakitu
What you get
- Presence at a glance — a spinner for working, ⚠ for "needs you", ◐ for waiting-on-a-peer, dimmed when stale.
- Per-agent inboxes — agents message each other and you; reply, delete, or turn a message into a task right from the cockpit.
- Tasks — a private, compaction-surviving to-do list per agent (and yours), optionally hung off a PR.
- Personas — each agent keeps a self-authored identity + private notes on teammates that reload every session.
- GitHub board automation (optional) — MCP tools to move cards, set/clear
blockers, and sweep agent PRs against a Projects v2 board. Configure the
default repo/board with
LAKITU_DEFAULT_REPO/LAKITU_DEFAULT_BOARD, or passrepo=per call. - Multi-machine — run
lakitu-mcp serveon a host and point remote agents + a remote cockpit at it. Seedeploy/REMOTE.md.
Configuration (env)
| Variable | Used by | Meaning |
|---|---|---|
LAKITU_FLEET_ROOT | all | Store location (default ~/.claude/lakitu-fleet). |
LAKITU_FLEET_NAME | hooks/agents | This agent's stable name. |
LAKITU_DEFAULT_OWNER | lakitu | Optional override for the owner prepended to bare repo names. By default the owner is inferred from the registered agents' repos, so this is rarely needed. |
LAKITU_DEFAULT_REPO | lakitu-mcp | owner/name default for board tools. |
LAKITU_DEFAULT_BOARD | lakitu-mcp | owner/projectNumber board fallback. |
LAKITU_FLEET_SERVER / LAKITU_FLEET_TOKEN | remote | Daemon URL + bearer token. |
License
Licensed under either of MIT or Apache-2.0 at your option. Unless you state otherwise, any contribution you submit shall be dual-licensed as above, without additional terms.