NTM

NTM - Named Tmux Manager

NTM turns tmux into a local control plane for multi-agent software development.
It combines session orchestration, graph-aware work triage, safety policy and approvals,
Agent Mail coordination, durable state capture, machine-readable robot surfaces, and a
local REST/WebSocket API in one Go binary.

TL;DR

The Problem

Running several coding agents in parallel is easy to start and annoying to sustain.
Plain tmux gives you panes, but it does not give you durable coordination, work
selection, safety policy, approvals, history, replayable automation surfaces, or a
shared control model that both humans and agents can use.

The Solution

NTM gives you a single local system for:

- spawning labeled multi-agent sessions in tmux
- sending work, interrupts, and follow-ups across panes
- triaging what to do next with br and bv
- coordinating agents with Agent Mail, file reservations, and assignments
- protecting dangerous operations with policy, approvals, and guards
- exposing the whole system through --robot-*, REST, SSE, WebSocket, and OpenAPI
- capturing state with checkpoints, timelines, audit trails, and pipeline state

Why NTM

Quick Start

Requirements

NTM is a pure Go project, but the runtime experience is intentionally integration-heavy.

- Required: tmux
- Required for agent spawning: whichever CLIs you want to run, typically Claude Code, Codex, Antigravity CLI, Oh My Pi (omp), or Grok Build (Gemini CLI is supported as legacy)
- Optional but powerful: br, bv, Agent Mail, cass, dcg, pt
- Sanity check everything with ntm deps -v

First Session

Core Workflows

1. Multi-Agent Session Orchestration

NTM is built around named tmux sessions with explicit agent panes and a user pane.
It handles session naming, pane layout, agent startup, labels, and…