Codeman vs Claude Code UI (CloudCLI): chat UI or live terminal
On this page
What CloudCLI isWhat Codeman isSide by sideChoose CloudCLI if...Choose Codeman if...Using bothClaude Code UI, now called CloudCLI, gives Claude Code, Codex, Cursor CLI and OpenCode a chat-style web interface with a file explorer, a git panel and a shell, and it offers a paid hosted version. Codeman streams each agent's own terminal from persistent tmux sessions, so pick CloudCLI if you want a chat view with IDE-like panels or a managed cloud setup, and Codeman if you want the CLI's real interface kept alive in tmux with no time limit, across server restarts too, with alerts on your phone.
What CloudCLI is
CloudCLI (the repository is still siteboon/claudecodeui) is an open-source web UI you start with npx @cloudcli-ai/cloudcli on Node.js 22+. It opens on port 3001 and discovers your existing sessions from ~/.claude. Conversations happen in a chat interface: it drives Claude Code through the Claude Agent SDK and Codex through the Codex SDK, and runs the Cursor and OpenCode CLIs as headless child processes. A chat run keeps going on the server when the browser disconnects and replays when it reconnects. Around the chat it has a Shell tab that opens the selected session in the agent's own CLI (or a plain shell), a file tree with editing, a git explorer for staging, committing and switching branches, and git worktree management added in v1.37.0. MCP servers you add in the UI are written to each agent's own config. A built-in Send later (since v1.37.3) queues a message for an existing session at a time you pick. A plugin system adds tabs and services; its plugin list includes an official web terminal and a community scheduler for recurring prompts. Its settings offer web push, desktop-app and sound notifications for action required, stop and error events.
CloudCLI's own Allowed Tools list starts empty: in the default mode, a Claude Code tool use that the CLI would ask about shows a prompt in the chat and is denied if nobody answers within 55 seconds. Read-only actions and rules already in your Claude settings files run without asking, and you can allow a tool from that prompt or in settings, or pick another permission mode in the composer. An opt-in Browser Use mode lets agents drive a real browser through an MCP server, and a REST API is available in every mode. Beyond self-hosting there is CloudCLI Cloud, a hosted environment from €7 per month that keeps agents running with your laptop closed, plus an optional desktop companion for macOS and Windows and experimental Docker sandboxes for Claude Code and Codex. The code is AGPL-3.0-or-later.
What Codeman is
Codeman is a self-hosted web server that runs agent CLIs inside persistent tmux sessions and streams each real terminal to a browser. It supports ten CLIs (Claude Code, Codex, OpenCode, Gemini CLI, Antigravity, Pi, Grok Build, DeepSeek Harness, OMP, GitHub Copilot CLI) plus plain shells, flags waiting or blocked agents on their tabs and through web push, and for Claude sessions adds auto-resume after a usage limit and live subagent windows. Cron jobs, Docker containers and remote SSH sessions are built in. It needs Node.js 22+ and tmux, runs on macOS and Linux (Windows through WSL2), and is MIT licensed.
Side by side
| CloudCLI | Codeman | |
|---|---|---|
| How you see the agent | Chat interface, plus a Shell tab that opens the session in the agent's own CLI | The CLI's own terminal, streamed live |
| Agents | Claude Code, Codex, Cursor CLI, OpenCode | Ten CLIs plus shell (Agent CLIs) |
| Hosted option | Yes, CloudCLI Cloud from €7/month | No, self-hosted only |
| Self-hosted | Yes, npm | Yes, installer or npm (Installation) |
| Phone access | Yes, responsive web UI, installable as a PWA | Yes: touch terminal, installable web app, QR login (Mobile Guide) |
| Notifications | Yes: web push, desktop app, sound | Yes: tab alerts, desktop, web push with optional Approve and Deny for Claude |
| File browsing and editing | Yes | Yes (Working With Files) |
| Git panel (stage, commit, branches) | Yes | No |
| Git worktree management | Yes, since v1.37.0 | Yes: create, open and remove from the case picker, local cases only (Git Worktrees) |
| Plugins | Yes | No; HTTP API, SSE and hooks instead |
| Default Claude permissions | Its own allow list starts empty: Claude asks in the chat before edits and most commands, unless your Claude settings already allow them | Permission prompts skipped by default; auto mode, normal prompting or an allowlist selectable |
| Terminal kept after you disconnect | Partial: the Shell tab's PTY stays 30 minutes after the last disconnect, per its source; chat runs continue on the server | Yes: tmux, including across server restarts |
| Resume after a usage limit | Not documented; it shows when the limit resets | Yes, Claude sessions only |
| Scheduled prompts | One-off Send later built in; recurring via a community plugin | Built in (Cron Jobs) |
| Isolation | Experimental Docker sandboxes (microVM; Claude Code and Codex only); CloudCLI Cloud runs each environment in its own container | Docker cases, one container per project (Docker Cases) |
| Desktop app | Yes, companion for macOS (Apple Silicon) and Windows | No; the web UI installs as a PWA |
| License | AGPL-3.0-or-later | MIT |
Choose CloudCLI if...
- You prefer reading and writing to agents in a chat layout, with the files, the git state and a shell in panels around it.
- You want someone else to host it. CloudCLI Cloud runs the environment for you; Codeman has no hosted version, and reaching it from a phone means setting up Tailscale, a tunnel or a LAN password yourself.
- You use Cursor CLI, which Codeman does not run.
- You want to stage, commit and switch branches from the UI, or add plugins.
- You want the more conservative default. CloudCLI's own allow list starts empty, so Claude asks before edits and most shell commands, while Codeman starts Claude sessions with permission prompts skipped unless you change the setting.
Choose Codeman if...
- You want the agent's actual TUI as the main view, slash commands, dialogs and all, kept alive in tmux, rather than in a Shell tab whose process CloudCLI ends 30 minutes after your last browser disconnects.
- Sessions must outlive the browser, the network and a restart of the server; in Codeman they live in tmux (Core Concepts).
- You run long unattended Claude sessions and want them to resume after a usage limit and show subagent activity as it happens (Keeping Agents Running).
- You use Gemini CLI, Antigravity, Pi, Grok Build, DeepSeek Harness, OMP or GitHub Copilot CLI, none of which CloudCLI's UI drives (its UI dropped Gemini CLI in v1.36.1, although CloudCLI Cloud still pre-installs Gemini CLI in its environments).
- You need one Docker container per project, agents on remote hosts over SSH, or recurring scheduled prompts built in.
Using both
They can run on the same machine: CloudCLI defaults to port 3001 and Codeman to 3000. Both read Claude Code's own transcripts under ~/.claude, so a Claude conversation started in one shows up in the other's history. Avoid driving the same conversation from both at once. A workable split: CloudCLI for focused work in the chat view, Codeman for sessions you leave running and check from your phone.
First checked against CloudCLI's README on 2026-09-25; checked again against its README, release notes and source (v1.37.5) on 2026-10-19 (14,166 stars). Spotted something out of date? Open an issue.