clamor

ORCHESTRATE THE NOISE

Tmux for agents. Because one isn't loud enough.

A terminal multiplexer for managing parallel coding agent sessions.

Why

You're running five coding agent sessions in parallel. Tab names blur together. You can't tell which agent needs input and which is still working. Switching between them means hunting through tmux windows or terminal tabs. Spawning a new one is a ritual of cd, naming, and arranging.

Clamor fixes this without replacing your workflow. It's not a new terminal, not a new editor, not an IDE that swallows everything. It's a single tool that does one thing well: manage parallel agent sessions. It runs inside your existing terminal, alongside tmux, inside whatever setup you already have. Unix philosophy — small, composable, stays out of the way.

Features

Persistent sessions — Agents live in a background daemon, not your terminal. Close the dashboard, reopen it — everything's still running. Terminal crash? SSH disconnect? Doesn't matter.

Jump keys — Each agent gets a home-row key (a/s/d/f/j/k/l/h, overflow to 1–0). One keypress to attach, Ctrl+F to detach. Switching between agents is instant.

Live state tracking — The dashboard shows each agent's actual state (working/waiting/done). Spot stalled agents immediately.

Color-coded title bar — When attached, a title bar shows the project name and a distinct color so you always know where you are. No squinting at tab names.

Auto-resume — The daemon automatically resumes agent sessions on restart. Terminal crash, SSH disconnect, daemon restart — agents pick up where they left off.

Session adoption — Already have agent sessions from before? Press R in the dashboard to adopt an existing session into Clamor.

Batch operations — Select multiple agents with v, select all with V, then act on the selection. Filter agents by name with /.

Non-blocking hooks — State tracking uses non-blocking file locks. Clamor never slows down your agent sessions.

Quick start

Install

cargo install clamor

Or build from source:

git clone https://github.com/amenocturne/clamor.git
cd clamor
cargo build --release
cp target/release/clamor ~/.local/bin/

Hook setup

Clamor tracks agent state (working/waiting/done) via hooks. For Claude Code, add these to your .claude/settings.json:

{
  "hooks": {
    "SessionStart": [{ "type": "command", "command": "clamor hook" }],
    "Notification": [{ "type": "command", "command": "clamor hook" }],
    "PreToolUse": [{ "type": "command", "command": "clamor hook" }],
    "UserPromptSubmit": [{ "type": "command", "command": "clamor hook" }],
    "Stop": [{ "type": "command", "command": "clamor hook" }]
  }
}

That's it — no files to copy. The hook reads events from stdin and updates agent state in ~/.clamor/state.json.

Configure folders

clamor config init    # Write starter config with built-in backends
clamor config         # Open config in $EDITOR

Config lives at ~/.config/clamor/config.yaml. Legacy ~/.clamor/config.json is auto-detected — run clamor config migrate to convert.

Folders

Each folder is a project directory where agents can be spawned:

folders:
  my-app:
    path: ~/projects/my-app
    backends: [claude-code, open-code]  # Which backends are available here

  scripts:
    path: ~/scripts  # Omit backends → defaults to [claude-code]

When a folder lists multiple backends, the spawn prompt shows a backend selector you can cycle through with arrow keys. The selection is persisted per folder.

Backends

Backends define how to spawn and resume agent sessions. Three are built-in (claude-code, open-code, pi) — you can override them or define your own:

backends:
  claude-code:              # Override a built-in
    display_name: Claude
    spawn:
      cmd: [claude, "{{prompt}}"]
      env:                  # Optional extra environment variables
        CLAUDE_CODE_MAX_TURNS: "50"
    resume:
      cmd: [claude, --resume, "{{resume_token}}"]
    capabilities:
      resume: true          # Can resume sessions after daemon restart
      hooks: true           # Supports clamor state tracking hooks
      sync_output_mode: true  # Uses synchronized output (BSU/ESU)

  my-custom-agent:          # Define a new backend
    display_name: Custom
    spawn:
      cmd: [my-agent, --prompt, "{{prompt}}"]

Template variables available in cmd:

Capabilities:

Use clamor config print-example to see a full config, or clamor config print-backend claude-code to see one backend's template.

Launch

clamor

Usage

clamor                  Open the dashboard (starts daemon if needed)
clamor ls               List all agents
clamor new <title>      Spawn a new agent
clamor attach <ref>     Attach to an agent (by ID or jump key)
clamor adopt <id>       Adopt an existing agent session
clamor edit <ref>       Update agent description
clamor kill <ref>       Terminate an agent
clamor kill --all       Terminate all agents
clamor clean            Remove finished agents
clamor config           Open config in $EDITOR
clamor config init      Write a starter XDG config
clamor config migrate   Copy legacy JSON config to XDG YAML
clamor config print-example
                        Print a full example config
clamor config print-backend <id>
                        Print one built-in backend template
clamor stop             Stop the daemon

Dashboard keys

Spawn prompt keys

Terminal keys

Architecture

Clamor uses a daemon-client architecture, similar to tmux:

┌──────────────┐    Unix socket    ┌────────────────────────┐
│              │◄─────────────────►│         Daemon         │
│   Dashboard  │  length-prefixed  │                        │
│  (TUI client)│       JSON        │  ┌───────┐ ┌───────┐   │
│              │                   │  │  PTY  │ │  PTY  │   │
└──────────────┘                   │  │ agent │ │ agent │…  │
                                   │  └───────┘ └───────┘   │
                                   └────────────────────────┘

• The daemon runs in the background, owns all agent PTY processes, and persists across dashboard restarts
• The dashboard connects over a Unix socket (~/.clamor/clamor.sock), subscribes to output streams, and renders the TUI
• State is tracked in ~/.clamor/state.json with file-locked reads/writes, updated by hooks in real time

Troubleshooting

Agent terminal looks garbled after attaching — Double Ctrl+F fixes it. The first detaches to the dashboard, the second re-attaches, resetting the terminal state.

Daemon won't start — Check if a stale socket exists: rm ~/.clamor/clamor.sock and try again.

Hooks not updating state — Verify that clamor is in your PATH and the hook entries are in your .claude/settings.json.

License

MIT