Walk away mid-run. Pick it up on your phone.

Sudo Dock is a local daemon that keeps every agent CLI you run going as a persistent chat on your own machine. Any browser attaches to the same live chat — laptop, tablet, phone — and Pulse tells you which ones are waiting on you.

  • claude
  • codex
  • antigravity
  • pi / omp
  • grok
  • cursor agent
  • any terminal tool

It doesn't drive your CLI tools or own your conversations. It attaches to sessions the vendor tool already owns, reads the session files they already write, and resumes with each tool's own --resume. Uninstall Sudo Dock and every session still opens fine without it.

Want a second pair of eyes? Send someone a link, read a six-digit PIN out loud, and they're in that one chat from their own browser. Nothing installed, nothing else exposed →

invite-only · every install set up with you, one to one

Sudo Dock in a desktop browser. The sidebar lists six sample chats across three demo projects, one working, one with a question, two marked Done. The open chat shows Claude's reply with an interactive bar chart of latency by region rendered inside the message.
A phone browser on a sample chat where Claude asks which label a settings tab should use, with the two answers shown as tappable options.
Browser captures of the real app (the October 30 build) running on a demo workspace. The projects, chats and the chart are sample data, not anyone's work.

Pulse

Six agents running. One needs you. Pulse says which.

Run six agents and the hard part stops being the typing. It's knowing which one finished, which one is stuck on a question, and which one went quiet an hour ago. Pulse is the home screen that answers that: one activity trace per project, and every open chat sorted into Needs you, Stalled, In motion, Sign-off, Done and Unread.

  • Work the queue from the keyboard. Reply, close with a note, snooze, sign off, reopen: one key each, and Undo on the ones that move a chat.
  • Snooze until something happens, not only until a time: until the chats under it finish, or until another chat you pick is done.
  • Priority bands. Mark a chat High or Low and the sidebar sorts by it. High chats are never shelved automatically.
  • See the ask without opening the terminal. With Sudo Dock's optional Claude hooks on, a chat waiting for approval names what it wants to run, such as Bash: git push.
The Pulse view on a sample workspace: a heartbeat header, the line '1 chat is waiting on you', activity traces for three demo projects, and lane counts of 1 Needs you, 3 In motion and 2 Unread.
Pulse on the same demo workspace, with sample chats.

On your phone

Built for the phone in your pocket, not a shrunken desktop.

The phone was the reason this exists, and a lot of October went to it. The same chats, the same live state, with controls sized for a thumb.

  • Swipe instead of squint. Swipe a chat row for Shelve, Snooze, Interrupt or Archive. Swipe the title bar to walk to the next chat; swipe the body to flip between CLI and Chat.
  • Answer with a tap. When Claude asks a multiple-choice question, the options show as buttons in the chat and on the sidebar preview card.
  • Talk instead of type (optional). Tap the mic, tap Stop, and the transcript lands in your draft to read first. Nothing is sent for you.
  • It reconnects by itself after the phone sleeps or changes networks, and the keyboard stays down until you tap a field.
  • Push notifications when a background chat finishes, even with Sudo Dock closed.
The phone sidebar drawer listing sample chats grouped under Today and This week, with working, question and Done states.
A sample chat on the phone where Claude's question shows two tappable answers, Billing and Plans.
Phone-width browser captures of the demo workspace. Sample data.

Guest access

Hand someone a seat without giving them anything.

You're deep in a session and want a second pair of eyes. From the chat menu you create a one-use link and a six-digit PIN. They open it in their own browser and they're in the same live conversation — nothing installed, no account, no access to your machine.

They see that one chat. Not your sidebar, not your projects, not your terminal, not a filesystem path, not a byte of PTY output from anything else. You pick read-only or can-ask-questions and the daemon enforces it — a read-only guest has no composer, and the server refuses the send even if they forge one. Their messages arrive attributed.

Invite several people to the same chat and each one is independent — own name, own mode, own expiry. Extend one, revoke another, and nobody else's session drops. Sessions you can hand out, seat by seat.

— built it to pull my son into a live session to help. No install on his end, just a URL and a PIN read out loud.

What's actually built

Ten things that work today. None of them is a roadmap.

Everything here is on current main and in daily use. Where a tool only exposes part of a thing, or a feature is off until you turn it on, the card says so.

anything that runs in a terminal
If it runs in a terminal, it opens as a chat — your own scripts, a local-model CLI, a tool I've never heard of, a tool that competes with this one. No adapter is required to run something. Adapters are enrichment on top: Claude Code, Codex, Google's Antigravity CLI (which replaced the Gemini CLI for personal sign-ins), Pi / oh-my-pi, Grok and Cursor's agent get named chats, resume, and a working / waiting-on-you / idle / complete state where the tool exposes enough to tell.
a chat view that reads like a chat
Flip any agent chat from the raw terminal to a readable transcript: Markdown, tables that wrap, tool steps folded into one line, compaction summaries collapsed. The top shows the last thing you asked and, when the chat is waiting, what it needs from you. A linked pull request shows as a card in the chat.
inline visuals
Ask a Claude, Codex or Antigravity chat to show something "as an inline visual" and its chart, diagram or clickable mockup renders inside the reply, desktop or phone. The page runs in a locked-down frame: no network, no forms, no access to Sudo Dock.
sessions that outlive the daemon
PTYs die when the daemon restarts; your conversations don't. Sudo Dock relaunches each chat with the tool's own resume command and refuses visibly rather than silently starting a fresh session if a resume isn't safe. Mark a chat keep-alive and it comes back on its own.
any browser is a full client
The daemon binds loopback by default; pair a second device with a six-digit PIN and it attaches over WebSocket to the same chats. Several browsers can watch and drive one session at once — close one, the chat keeps running on the daemon. Set a public URL and the chat links your agents hand you open on your phone. It stays responsive with a dozen agents working at once.
files and a checklist per chat
A Files panel beside the chat finds files by name or searches their contents, and opens a hit at its line. Each chat also keeps a checklist that you and its agent can both update; "Update from chat" asks the agent to tick off what it finished.
accounts and limits
One page for every account's quota windows, with a projection of whether this week's usage runs out before the reset. Pin one account and Sudo Dock moves new chats to the next one at a point you set (80% to start). Chats already running never move.
a control API for your own agents
A separate, token-authenticated API lists, spawns, prompts, reads and waits on chats, with per-token scopes and grants. It ships as a WebSocket, a CLI (sudock control …) and an MCP server, so one agent can coordinate others, and the workers it starts can carry the project's goal and standing instructions.
cross-tool history + search
Sudo Dock indexes the session files your agents already write, including ones started before Sudo Dock existed, plus import-only history from Claude Desktop. Cmd+K searches live chats, archived ones, past sessions and the text of conversations.
chats in Telegram optional
Point a Telegram bot at a project and each open chat gets its own topic. Final answers arrive there; reply to queue a message, steer or stop a working chat, press keys on a terminal prompt with buttons, or send a photo, a file or a voice note.
group chat early
Several agent chats merged into one routed conversation, addressed by @alias, with no message store of its own. In daily use, and still being shaped by what real sessions teach.

Your machine. Your code. Your sessions.

The daemon runs where your work already lives. The PTYs are local, the session files are local, the git history is local. Sudo Dock is the browser-accessible layer in front of it — not a cloud dev host, and not a place your code goes. Remote access is whatever you already run: your LAN, your Tailscale, your tunnel. Got a second box? Run another daemon there — in Docker on a server, or in the background on a Mac — and reach it the same way.

Why this exists

SSH from a phone is surgery through a keyhole.

I kept wanting to check on long-running agent sessions from my phone — approve a command, read what an agent had done, nudge it and walk away again. The obvious answer was "just SSH in." SSHing into your machine from a phone is miserable: tiny keyboard, no real terminal, dropped connections, squinting at a session you can barely scroll.

So Sudo Dock is the thing I wanted instead. A daemon runs on the machine where the code, the git history, and the CLI agents already live. It owns the terminal sessions. Any browser — laptop, tablet, phone — attaches over a WebSocket and sees the exact same live state. Close the lid, pick up the phone, tap into the chat, and it's the session that never stopped running.

It's been my daily driver for months. Everything on this page is something I use, not something I plan.

Invite-only

No installer. I set it up with you.

Every Sudo Dock install is done one to one, on your machine, with you. We wire in the agents you already run, pair your phone, and walk the daily loop together, so you leave the session using it, not reading about it.

you want to use it

You run two or more agent CLIs and leave sessions going. Request an invite and tell me your setup. If it's a fit, we book a session and install it together. After that you have a direct line to the person who builds it, and Help carries 15 step-by-step guides for the rest.

Linux, macOS or Windows (native or WSL), or Docker. Nothing leaves your machine.

you want to help build it

The most obvious surface is CLI adapters — teaching Sudo Dock to read a tool it doesn't know yet, against a small documented interface. Beyond that: phone input, group-chat routing, and agents that drive other agents over the control API.

Code contributions open once a CLA is in place. Tell me what you'd work on and I'll walk you through the code.

Request an invite

Straight to my inbox. No list service, no drip sequence — I read every request and reply myself.

Which are you? optional

Status

The fine print, up front.

  • Version 0.8, in active daily development. It changes often, and it says so: every update lists what changed inside the app.
  • AGPL-3.0-only. Self-hosting is free, forever. A commercial license exists for running a modified Sudo Dock as a closed network service.
  • Linux and macOS, native. Windows runs native via ConPTY, or inside WSL if that's where your CLI agents already live. Docker and a Windows desktop app (preview) too.
  • Source is private for now. It runs a terminal on your machine, so the public release gets done carefully and once. Invitees can ask for a walk through the code.
  • Code contributions open once a CLA is in place. Bug reports with clear repro steps are welcome now, and so is the problem you're hitting.