Dicklesworthstone/ntm
Named Tmux Manager: spawn, tile, and coordinate multiple AI coding agents (Claude, Codex, Gemini) across tmux panes with a TUI command palette
NTM – Named Tmux Manager
What it is – NTM is a Go‑written command‑line tool that turns a local tmux session into a tiny “control plane” for running multiple AI coding agents side‑by‑side with a human operator. It adds a layer of orchestration, safety checks, work‑tracking and a programmable API on top of plain tmux.
Why it matters – Running several LLM‑powered coding assistants (Claude, Grok, Oh My Pi, etc.) in parallel is possible with tmux, but you quickly lose coordination: you can’t see which agent is working on what, you can’t enforce policies, and you have no durable record of what was done. NTM fills that gap by giving each agent a labelled pane, a persistent work‑graph, reservation/locking of files, and a REST/WebSocket interface that scripts or other tools can call.
Key features
| Area | What NTM does | Typical commands |
|---|---|---|
| Session orchestration | Creates named tmux sessions, spawns labelled agent panes, lets you zoom, attach, view a dashboard or palette. |
ntm spawn api --cc=2 --cod=1, ntm dashboard api |
| Work intelligence | Integrates with br/bv issue trackers to triage the next task, analyse impact, and auto‑assign work to specific agents. |
ntm work triage, ntm assign payments --auto |
| Coordination | Provides “Agent Mail” inboxes, file‑reservation locks, and per‑agent Git worktrees so agents don’t step on each other. | ntm mail send …, ntm locks list, ntm worktrees merge |
| Safety | Guards destructive commands, enforces policy files, and requires explicit approvals for risky actions (e.g., force‑releasing a lock). | ntm safety, ntm approve <id> |
| Durability | Saves checkpoints, timelines and audit logs; you can restore a session later. | `ntm checkpoint save api -m |
Related
- Project
- Project
- Project
- Project
- Project