Introduction
codeout is a self-hosted GUI for your AI coding agent. A small daemon runs on your own machine, starts the agent, keeps each session alive, and serves it to your phone or browser over an end-to-end encrypted channel. Each session is either a clean chat or a raw terminal, your pick.
The one-paragraph pitch
You already run Claude, Codex, Gemini, or OpenRouter in a terminal on the machine where your code lives. codeout puts that session on the device in your pocket and gives you a real chat UI over it: streamed replies, reasoning traces, tool cards, and an approval prompt every time the agent wants to run a command. The agent runs where your files, your tools, and your credentials already are. The display runs wherever you happen to be standing. Nothing in between gets to read either one, because the channel between your device and your daemon is encrypted end to end. There is no cloud account to create, no relay server holding your sessions, and no company sitting in the path. Your devices connect to your daemon, and that is the whole list of computers involved.
If you have ever wanted to check on a long-running refactor from the sofa, approve a risky command from a train, or read what your agent did overnight without opening the laptop, that is the entire idea. The hard part, keeping a real agent session alive and reachable without leaking it to a third party, is what codeout does for you.
What you get
Chat mode, the headline
A messaging UI over your agent: streamed replies, thinking traces, markdown, collapsible tool cards, slash commands, and a tap to Allow or Deny each tool the agent wants to run.
Terminal mode, when you want it
Start a session as a terminal instead of a chat and you drive the raw PTY. Full-screen TUIs render properly, colours and cursor and all. If it works in your shell, it works in codeout.
Sessions that survive
Close the tab, lose signal, restart the daemon. The session keeps running and your 1:1 chat history and uploaded files replay right where you left them.
Encrypted end to end
libsodium session keys, paired by QR or a typed code. Over the public tunnel, only sealed ciphertext crosses the wire, and only paired devices get in.
codeout orchestrates Claude (claude), Codex (codex), Gemini (gemini / agy), and OpenRouter (with built-in tool execution). Configure model allowlists, toggle OAuth vs direct API keys, test connection latencies, and scan visual pairing QR codes from the local Host Control Deck at http://localhost:8400/. Any session can also be a plain shell, with no agent at all.
What codeout is not
codeout does not host your agent for you, and that is deliberate. It will not sign you up, will not store your keys, and will not proxy your traffic through somebody's data center. It is not a hosted IDE and it is not a chat front end bolted onto an API. It runs the tools you already have, with the config you already wrote, on the machine you already trust.
It is also not magic. The daemon has to be reachable from your device for any of this to work. On the same network that is automatic. From the wider internet you bring a path, and codeout makes that easy without ever weakening the encryption. See Remote access for the three ways to do it.
Where to start
If you just want it running, go to Quick Start. To understand the moving parts first, read How it works, then Security and encryption.
Need help?
Questions, bugs, or feature requests: email [email protected] or open an issue on GitHub. See Support for all the ways to get help, and Privacy for how your data and the AI agent are handled.