Agent Manager
Coding · tested 2026-08-18 · re-test due 2026-11-16 · by the Hlido desk, not the vendor
In short: A fast, keyboard-driven control tower for running many coding agents at once — spawn in a sentence, answer a blocked one without attaching, review its diff in place — and it runs your real installed CLIs as-is rather than reimplementing them.
Quick answer
Agent Manager scores 73/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-18). STEADY (73) because it delivers a genuinely polished, differentiated workflow for a real emerging need — managing many parallel coding agents from one keyboard-driven list — composes with users' existing CLIs rather than Pricing: Open source (free entry point documented).
Agent Manager is a well-executed answer to a problem that is suddenly real: developers now run five, ten, twenty coding-agent sessions in parallel, and a wall of tmux panes is a poor way to manage them. Built in Go on tmux, Apache-2.0, installable via Homebrew on macOS, Linux and WSL, it turns that fleet into a single navigable list where every action is one keypress — space to spawn an agent from a one-sentence task into the right directory, space again on a session row to answer a blocked agent in place without attaching, ctrl+r to open a full review mode with per-file diffs and inline comments, and worktree spawns for work that needs its own branch. The design decisions are thoughtful: sessions rename themselves once the agent knows the task; folded groups keep per-status counts so a collapsed subtree still tells you if something is blocked on you; state (arrangement, groups, archives) survives restarts. Crucially, each session runs your own installed CLI as-is — your login, your config, your MCP servers — so it composes with Claude Code, Codex, OpenCode, Grok and others rather than locking you into one. For Claude Code it reads real hook events instead of guessing pane state, which is the right way to detect status. It has genuine early traction (Hacker News, Product Hunt, Trendshift, TLDR). The honest limits are stage-typical: it is a solo, open-source project, terminal-only, tmux- and Unix-centric (no native Windows outside WSL), and there is no independent reliability or scale evidence beyond the launch coverage. As a power-user workflow layer for multi-agent coding, it is polished and clearly differentiated.
Why STEADY
STEADY (73) because it delivers a genuinely polished, differentiated workflow for a real emerging need — managing many parallel coding agents from one keyboard-driven list — composes with users' existing CLIs rather than replacing them, uses real hook events for Claude Code status, and shows early independent traction. Not VITAL because it is a solo open-source project, terminal- and tmux-centric with no native Windows path, and carries no reliability, scale or sustained-adoption evidence beyond launch coverage.
What it does well
- Spawns an agent from a one-sentence task with a single keypress, directory and prompt already set — no form, no cd
- Answers a blocked agent in place (reply lands in its pane) without attaching or switching tabs
- Runs your own installed CLI as-is — your login, config and MCP servers — across Claude Code, Codex, OpenCode, Grok
- Built-in review mode (ctrl+r): per-file diffs, four scopes, split/unified, and inline comments from the list
- Detects Claude Code status from its real hook events rather than guessing at the pane
- Groups, ordering, folds and archives persist across restarts; folded subtrees still show per-status counts
What it fails at
- Solo, open-source project — continuity and support depth are unproven
- Terminal- and tmux-centric; no native Windows support outside WSL
- No independent reliability, scale or sustained-adoption evidence beyond launch-week coverage
- Assumes comfort with a keyboard-driven TUI and Unix tooling — not for GUI-first users
- Some navigation features are explicitly in beta on the surface
Best for
- Developers running many parallel coding-agent sessions who want one keyboard-driven place to control them
- Teams mixing multiple agent CLIs (Claude Code, Codex, OpenCode) who want each run to keep its own config and MCP servers
- Power users who want in-place diff review and inline comments without leaving the session list
- macOS/Linux/WSL users comfortable in a tmux-based terminal workflow
Not recommended for
- Windows-native users who cannot or will not run under WSL
- GUI-first developers who prefer an IDE panel over a terminal TUI
- Buyers who require vendor-backed support and reliability guarantees
- Single-agent workflows where a fleet manager adds no value
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-18.
Compared to
-
persistproc
multi-agent-session-orchestration
Both help humans and agents run software locally, but they target different layers: Agent Manager orchestrates the agent sessions themselves (spawn, answer, review many coding agents), while persistproc manages the long-running processes (dev servers, databases) that agents need to see and control. They are complementary — a session manager over agents versus a shared process layer under them — more often than alternatives.
Agent relevance
CLI MCP Behavioral-testable
Agentic-Commerce Readiness 57/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
Agent Manager is a manager OF agents rather than an agent with a callable surface: it spawns and controls coding-agent CLIs, and exposes MCP tools an agent uses to declare the repo/worktree and merge base it moved into so review-mode targets correctly. It runs Claude Code, Codex, OpenCode and Grok as-is, preserving each one's own MCP servers. Direct relevance to any multi-agent coding workflow; the value is orchestration, not a drivable API.
Agent-friendly score: 8/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Go + tmux, Apache-2.0, installable via Homebrew on macOS, Linux and WSL — source (2026-08-18) verified
- Spawn, answer-in-place, and review-mode (ctrl+r) all one keypress from the list — source (2026-08-18) verified
- Runs your own installed CLI as-is; Claude Code status from real hook events — source (2026-08-18) verified
- Independent launch coverage (Hacker News, Product Hunt, Trendshift, TLDR) — source (2026-08-18) verified
- Independent reliability or scale benchmarks — source (2026-08-18)