Introduction
codeout is a self-hosted GUI for your AI coding agents. A small daemon runs on your own machine, starts the agent, keeps the terminal session alive, and serves it to your phone or browser over an end-to-end encrypted channel.
The one-paragraph pitch
You already run Claude, Gemini, or a plain shell in a terminal on the machine where your code lives. codeout puts that exact session on the device in your pocket. 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, kick off a build 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 terminal alive and reachable without leaking it to a third party, is what codeout does for you.
What you get
Any agent, per session
Start Claude, Gemini, or a raw shell. Each session picks its own agent, and you can run several at once across projects and machines.
Real terminals, not a chat box
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, switch devices. The session keeps running on the daemon and is right where you left it when you return.
Encrypted end to end
libsodium session keys, paired by QR or a typed code. No relay server ever sees plaintext, and a tunnel only ever carries sealed ciphertext.
What codeout is not
codeout does not host your agents 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.