Run NTM for multi-agent tmux orchestration, work triage, robot mode, safety, coordination, and local APIs. Use when spawning swarms, dispatching work, or operating ntm as an agent or human operator.
$npx -y skills add dicklesworthstone/ntm --skill ntmInstalls into the current project.
Run `npx skills use "https://github.com/dicklesworthstone/ntm" --skill "dicklesworthstone/ntm"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/dicklesworthstone/ntm" that are relevant to the current task. Run `npx skills add "https://github.com/dicklesworthstone/ntm"` and select the relevant skills, then follow their instructions.
| 1 | # NTM - Named Tmux Manager |
| 2 | |
| 3 | <div align="center"> |
| 4 | <img src="ntm_dashboard.webp" alt="NTM dashboard"> |
| 5 | </div> |
| 6 | |
| 7 | <div align="center"> |
| 8 | |
| 9 |  |
| 10 |  |
| 11 |  |
| 12 |  |
| 13 | |
| 14 | </div> |
| 15 | |
| 16 | NTM turns `tmux` into a local control plane for multi-agent software development. |
| 17 | It combines session orchestration, graph-aware work triage, safety policy and approvals, |
| 18 | Agent Mail coordination, durable state capture, machine-readable robot surfaces, and a |
| 19 | local REST/WebSocket API in one Go binary. |
| 20 | |
| 21 | <div align="center"> |
| 22 | |
| 23 | ```bash |
| 24 | curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/ntm/main/install.sh?$(date +%s)" | bash -s -- --easy-mode |
| 25 | ``` |
| 26 | |
| 27 | </div> |
| 28 | |
| 29 | ## TL;DR |
| 30 | |
| 31 | ### The Problem |
| 32 | |
| 33 | Running several coding agents in parallel is easy to start and annoying to sustain. |
| 34 | Plain `tmux` gives you panes, but it does not give you durable coordination, work |
| 35 | selection, safety policy, approvals, history, replayable automation surfaces, or a |
| 36 | shared control model that both humans and agents can use. |
| 37 | |
| 38 | ### The Solution |
| 39 | |
| 40 | NTM gives you a single local system for: |
| 41 | |
| 42 | - spawning labeled multi-agent sessions in `tmux` |
| 43 | - sending work, interrupts, and follow-ups across panes |
| 44 | - triaging what to do next with `br` and `bv` |
| 45 | - coordinating agents with Agent Mail, file reservations, and assignments |
| 46 | - protecting dangerous operations with policy, approvals, and guards |
| 47 | - exposing the whole system through `--robot-*`, REST, SSE, WebSocket, and OpenAPI |
| 48 | - capturing state with checkpoints, timelines, audit trails, and pipeline state |
| 49 | |
| 50 | ### Why NTM |
| 51 | |
| 52 | | Area | What NTM provides | Typical commands | |
| 53 | | --- | --- | --- | |
| 54 | | Session orchestration | Spawn, label, inspect, zoom, dashboard, palette | `ntm spawn`, `ntm dashboard`, `ntm palette` | |
| 55 | | Work intelligence | Graph-aware triage, next-step selection, impact analysis, assignment | `ntm work triage`, `ntm work next`, `ntm assign` | |
| 56 | | Coordination | Human overseer mail, inbox views, file reservations, worktrees | `ntm mail`, `ntm locks`, `ntm worktrees` | |
| 57 | | Safety | Destructive-command protection, policy editing, approval workflows | `ntm safety`, `ntm policy`, `ntm approve`, `ntm guards` | |
| 58 | | Durable operations | Checkpoints, timelines, audit logs, saved sessions, pipelines | `ntm checkpoint`, `ntm timeline`, `ntm audit`, `ntm pipeline` | |
| 59 | | Automation surfaces | Robot JSON, REST API, SSE/WebSocket streams, OpenAPI | `ntm --robot-snapshot`, `ntm serve`, `ntm openapi generate` | |
| 60 | |
| 61 | ## Quick Start |
| 62 | |
| 63 | ### Requirements |
| 64 | |
| 65 | NTM is a pure Go project, but the runtime experience is intentionally integration-heavy. |
| 66 | |
| 67 | - Required: `tmux` |
| 68 | - Required for agent spawning: whichever CLIs you want to run, typically Claude Code, Codex, Antigravity CLI, or Grok Build (Gemini CLI is supported as legacy) |
| 69 | - Optional but powerful: `br`, `bv`, Agent Mail, `cass`, `dcg`, `pt` |
| 70 | - Sanity check everything with `ntm deps -v` |
| 71 | |
| 72 | ### First Session |
| 73 | |
| 74 | ```bash |
| 75 | # Install |
| 76 | curl -fsSL "https://raw.githubusercontent.com/Dicklesworthstone/ntm/main/install.sh?$(date +%s)" | bash -s -- --easy-mode |
| 77 | |
| 78 | # Enable shell integration |
| 79 | eval "$(ntm shell zsh)" |
| 80 | |
| 81 | # Verify tools and integrations |
| 82 | ntm deps -v |
| 83 | |
| 84 | # Scaffold a project directory |
| 85 | ntm quick api --template=go |
| 86 | |
| 87 | # Launch a mixed swarm |
| 88 | ntm spawn api --cc=2 --cod=1 --agy=1 |
| 89 | |
| 90 | # Open the live operator surfaces |
| 91 | ntm dashboard api |
| 92 | ntm palette api |
| 93 | |
| 94 | # Dispatch work |
| 95 | ntm send api --cc "Map the auth layer and propose a refactor plan." |
| 96 | |
| 97 | # If the repo uses br/bv, inspect the work graph |
| 98 | ntm work triage --format=markdown |
| 99 | |
| 100 | # Save a recoverable checkpoint |
| 101 | ntm checkpoint save api -m "before auth refactor" |
| 102 | |
| 103 | # Expose local APIs for dashboards, scripts, and agents |
| 104 | ntm serve --port 7337 |
| 105 | ntm --robot-snapshot |
| 106 | ``` |
| 107 | |
| 108 | ## Core Workflows |
| 109 | |
| 110 | ### 1. Multi-Agent Session Orchestration |
| 111 | |
| 112 | NTM is built around na |