ntm

NTM (Named Tmux Manager) is a Go binary that turns tmux into a local control plane for running multiple AI coding agents in parallel. Rather than juggling raw tmux panes, it provides named sessions, labeled agent panes, a user pane, and a set of operator surfaces for dispatching work, monitoring progress, and recovering state. Core capabilities described in the README: - Session orchestration: spawn, add, list, inspect, zoom, attach, and view named tmux sessions with explicit agent panes. Supports labels so multiple coordinated swarms can share one project directory, and optional Git worktree isolation (one branch/worktree per agent) for independent checkouts. - Agent support: Claude Code, Codex, Antigravity CLI, Oh My Pi (omp), Grok Build, and Gemini CLI as legacy. Agent-specific launch flags, model/effort arguments, adopt-existing-pane flows, and per-agent readiness detection are documented, including omp TUI-derived state (ready/working/idle, provider errors, context gauge) and Grok Build phase-one limitations. - Dispatch and monitoring: broadcast prompts, interrupt panes, stream output, health checks, activity watch, response diffing, pane history search, and analytics. - Work graph triage: integration with br and bv for next-task selection, blockers, impact analysis, forecasting, and assignment to panes or agent types, with label-based authorization gates and a queue-dry/ideate flow for empty queues. - Coordination: Agent Mail messaging, inbox views, file reservations, lock renewal and approval-gated force-release, coordinator status/digest/conflict commands, and optional pane identity badges in tmux borders. - Safety and approvals: policy rules for allowed/blocked/approval-gated actions, destructive-command checks, durable approval workflows including two-person approval for high-risk operations. - Reusable automation: recipes, workflows (pipeline, ping-pong, review-gate), prompt templates, executable pipelines with variables, dependencies, resume and cleanup, and session templates. - Durable state: checkpoints, timelines, audit records, history search, conflict views, and session resume. - Automation surfaces: machine-readable --robot-* CLI commands (status, snapshot, plan, dashboard, send, ack, tail, mail-check, cass-search, etc.) and a local server exposing REST under /api/v1, SSE at /events, WebSocket at /ws, health at /health, and a generated OpenAPI spec. Installation is via a shell installer script, with shell integration for zsh and a dependency check command. The project is written in Go and requires tmux at runtime; agent CLIs are optional but needed for spawning. The README emphasizes integration-heavy operation and documents many optional companion tools (br, bv, Agent Mail, cass, dcg, pt). This overview reflects only what the repository documentation states; no performance, ranking, or adoption claims are made.