Codeman is a free, open-source web dashboard for AI coding agents. It runs Claude Code, Codex, Gemini CLI, OpenCode and five more agent CLIs 24/7 in persistent tmux sessions on your own machine. Watch and answer every agent from any browser, phone included.
curl -fsSL https://getcodeman.com/install | bash
Mac · Linux · Windows (WSL) · needs Node 22 + tmux · prefer npm? npm i -g aicodeman
Typing into a remote terminal normally means a 200-300ms round trip per keystroke, and seconds on a bad link. Codeman paints your keystrokes instantly in a Mosh-inspired local echo overlay, then hands off invisibly the moment the real echo arrives.
Extracted as a standalone library for any xterm.js app: npm i xterm-zerolag-input
You never run just one coding agent. Codeman puts all of them, across every project, in a single row of tabs with live status.
ssh still works like it always has.
xterm-zerolag-input on npm).
Hit Tiles and up to six sessions sit side by side in one window. Every tile is a real terminal you can type into, and its header shows which agent runs there, the model it's on, and whether it's working or waiting on you. Claude Code next to Codex next to DeepSeek, all at once, no tab switching.
Same as the Tiles button. Brings back the grid you had last, every tile where you left it.
Pick 2, 4 or 6 tiles. Your pick sticks on that device.
Swap two tiles, or drop one on an empty slot. Ctrl+Shift+Arrows does the same from the keyboard.
One tile fills the grid, one more click and the grid is back. Files, git and voice follow the tile you're in.
Every key and every detail: the Tile Grid docs · without Codeman: running many Claude Code sessions at once
Install the codeman skill and the agent inside a session can drive Codeman itself. Ask it in plain English and it starts worker sessions, hands each one its task, waits for them and reports back. Workers can run different harnesses side by side, and lineage lines show who spawned whom.
Install with codeman skill install, then just ask. The plugin route and every recipe: driving Codeman from an agent
Your agents print the paths of what they made. Click one and the picture, the video or the report opens right in the page, Markdown rendered. Fix a line, hit Save, and the file on disk changes. No SSH, no editor, and it works the same on your phone.
Every file type, the edit rules and downloads: Working With Files
Two short tours recorded on a live Codeman with real agents working: six sessions from one click, links that open files and videos in place, and answering an agent's question from the desktop or a phone.
Multi-layer idle detection (completion messages, output silence, token stability, an optional AI check) re-prompts a session that has genuinely stopped. Around 110k tokens Codeman triggers /compact, around 140k a full /clear plus re-init, and a circuit breaker trips on no-progress loops instead of burning tokens all night. Background: auto-continue after a usage limit and what lock, sleep and a closed lid do to Claude.
Opt-in per session, because auto-consuming your quota the moment it resets should be a deliberate choice. A built-in overnight-autonomous preset tunes all of it for unattended runs.
A tool you live in all day has to be keyboard-first. The speed that matters isn't benchmark speed; it's "check five agents, unblock two, queue one more, done in ninety seconds" speed.
A session palette: fuzzy-type any session or case name and jump. Behind it, a manager of every session you've ever run: searchable by prompt, pinnable, resumable.
Straight to any tab, cycle through them, and every shortcut is rebindable (Ctrl+? shows the map).
Pick a case, hit Run, the tab appears named and numbered. Need five agents on one repo? The tabs number themselves.
Cross-session search digs through session names, run events, and files the agents touched.
Recurring work doesn't need you: scheduled jobs launch an agent with a prompt, in any of the supported CLIs.
One click answers "what happened while I was gone": which sessions need attention, finished, or are still running.
Every agent sitting on a permission prompt, in one queue. Answer it from the drawer, or straight from the push notification, without hunting for the tab.
Your Grafana, your dev server, your dashboard: saved as a tab next to the agents, proxied through Codeman so it works from the phone too.
Stuck on what to type next? It reads the session and your recent prompts and drafts the next one. Nothing sends itself.
One dense dashboard at the desk, and the exact same live sessions from the phone in your hand: QR login, push notifications when an agent needs you, and typing that feels local even over a tunnel. Every way to use Claude Code from a phone.

Not on the laptop itself: closing the lid puts it to sleep, and a sleeping computer suspends every process (locking the screen does not). Install Codeman on any machine that stays on: a Mac mini, a home server, a VPS. Every agent runs there in a persistent tmux session, so closing your laptop changes nothing. Open a browser later and you're back in the same live session, full scrollback included. What lock, sleep and a closed lid each do.
Codeman reads the "limit reached, resets 8pm" message, parses the reset time, waits it out and continues the run automatically. It's opt-in per session, so consuming your quota the moment it resets is always a deliberate choice. Claude Code's own auto-continue, and when it does not fire.
Yes. Scan a single-use QR code to log in, get a push notification when an agent needs you, and type with zero perceived lag thanks to a Mosh-inspired local echo overlay. It's a real mobile client, not a shrunken desktop. All the ways to use Claude Code from a phone.
Yes: Claude Code, OpenCode, Codex CLI, Antigravity CLI, Gemini CLI, Pi (pi.dev), Grok Build, DeepSeek Harness and OMP all run as first-class session types, side by side in the same tab row, plus plain shell sessions. Gemini is enterprise-only since Google's consumer cutover, and Antigravity (agy) is Google's current CLI, so Codeman runs both.
Yes. Every session is its own tmux session and browser tab, tabs turn yellow or red when an agent needs you, and the tile grid shows up to six live terminals side by side. Give each session its own git worktree to avoid file collisions. Running many sessions without collisions.
Anthropic offers claude.ai/code for cloud sessions and Remote Control for a local one. Codeman is the self-hosted option: it streams the real Claude Code terminal, and Codex, Gemini CLI and six more CLIs, from your machine to any browser. How it compares with other web UIs.
Herdr is a strong terminal-first runtime that keeps agent processes alive on one machine. Codeman is web-first: the same persistent sessions, but streamed to any browser, with a real phone UI, tabs that blink when an agent needs you, push notifications, QR login and zero-lag typing over high-latency links. If you live in the terminal, Herdr fits great; if you want to reach your agents from anywhere, that is exactly what Codeman was built for. Nothing stops you from trying both. Codeman vs Herdr in detail, or every alternative.
It binds to loopback only by default, so nothing is reachable until you decide how to expose it: set a password and reverse-proxy it, or point Tailscale at the loopback bind. DNS-rebinding protection, an Origin/CSRF guard and rate-limited auth are always on.
Nothing. Codeman is MIT-licensed open source with no telemetry, no account and no cloud component; it runs entirely on your own hardware.
One command on any machine that stays on: a Mac mini in a closet, a Linux box, a VPS. The installer prompts before every system change and binds to loopback by default.
A dashboard that drives coding agents deserves paranoia about who can reach it. Defense in depth, always on:
curl -fsSL https://getcodeman.com/install | bash
MIT licensed · built by Ark0N · runs entirely on your own hardwaredocs · guides · compare · changelog · llms.txt