agentmux runs Claude Code, Codex, and Cursor sessions on your dev machine and lets you reach them from Telegram or a PWA. Spawn multiple agents, switch between them with /switch, keep them working while you're away from the desk.
Same idea as OpenClaw or Hermes, but specialized for coding agents and built on each vendor's official remote-control surface — Claude Code channels, the Codex app-server, and the Cursor CLI directly. No harness, no API proxy, no detection signature.
agentmux is a local daemon that supervises a session per coding agent and exposes a broker your phone can talk to. Each session uses the vendor's own remote-control interface, so the agents run on your box with your account — agentmux is just the remote, and the inbox that ties many sessions together.
Each session is its own supervised process with its own working directory, agent, and history. Spawn /new auth-refactor on the train, switch to /billing-rewrite for a quick question, leave them all running. The registry persists; sessions survive reboots.
No harness, no API proxy, no credential reads. agentmux talks to each agent through the same interface the vendor's own mobile/desktop apps use — so there's nothing for Anthropic's harness detection to flag, and nothing different for OpenAI to break. Subscriptions stay on subscription billing.
--channels MCP plugin protocolcodex app-server JSON-RPC — same as the desktop appcursor-agent --resume headless modeSlash commands the way you'd expect: /switch, /new, /sessions. Telegram does the heavy lifting — notifications, history, search, attachments. Works on any device that runs Telegram, which is most of them.
billing-rewriteThe PWA is the same broker, different surface. List of sessions like a messenger, tap in to chat with one agent. Push notifications when something finishes. Install it to your home screen; it behaves like a native app.
The broker speaks plain HTTP on localhost — point any tunnel at it. cloudflared is the tested path (and what the project ships docs for), but tailscale funnel, ngrok, or a self-hosted reverse proxy work the same.
agentmux is dogfooded from day one: this landing page, the Docker setup, and the mobile polish were shipped through the same remote agent workflow the project is built to enable.
It's a daemon, a broker, and a tunnel. No managed service, no account, nothing to sign up for.
The daemon owns the tmux session and the agent registry. Wraps whichever CLIs it finds on PATH — claude, codex, cursor-agent.
Cloudflared is what we tested. Any tunnel that fronts localhost will do — the broker doesn't care.
Set BOT_TOKEN, open the PWA URL on your phone, install to home screen. Same broker, two surfaces.
Three tools you've probably heard of. They overlap with agentmux in some ways and not at all in others. The biggest split is what each one is for, and how Anthropic treats it.
HERMES.md in repo triggers rerouteSources: Wikipedia: OpenClaw · Consumer Rights Wiki: HERMES.md billing flaw · TechCrunch (Apr 4, 2026). Anthropic's stated reasoning, via Boris Cherny: "subscriptions weren't built for the usage patterns of these third-party tools."
MIT-licensed, no telemetry, no servers in the path. Issues and PRs welcome.
Clone the repo on GitHub. Full setup guide ships when the project goes public.
Cloudflare is the tested path; tailscale funnel, ngrok, or your own reverse proxy work equally well.