Quick Start
Four steps from nothing to a live agent on your phone. Total time is about a minute, most of which is your camera focusing on a QR code.
1. Install
codeout ships as a single global package. Install it with bun or npm.
$ bun install -g codeoutcli # or $ npm install -g codeoutcli
That puts the codeout command on your path. The full list of requirements and the update routine live on the Install page if you want them.
2. Run the daemon
From the project directory you want to work in, start the daemon. By default it opens a public tunnel and prints a stable URL, terminal QR, and opens the local Host Control Deck on http://localhost:8400/.
$ codeout self-hosted AI coding agents, in your pocket opening tunnel (codeout.dev) ... ready Pair a device scan the QR, or type the codeaddress https://amber-cedar-204.codeout.dev code K7QM-3FBR-9TZX valid 5 min fingerprint 7Q3M-X2VD confirm this matches in the app Host Control Deck: http://localhost:8400/ Reachable from anywhere via the tunnel above. The link stays end-to-end encrypted. Ctrl-C to stop. Your sessions keep running and reattach next launch.
The daemon now holds the listener open and waits for a device. Leave this running. Everything you do happens inside this process.
3. Pair a device
On your phone or laptop, open app.codeout.dev (or the native iOS app) and point the camera at the QR (in your terminal or on the Host Control Deck at http://localhost:8400/), or use the scanner in the app. It carries the daemon address and a single-use pairing secret. Your device runs a key exchange, gets its own device token, and is paired. You do not type a password anywhere.
No camera handy? In the app, choose to pair manually, enter the daemon address, and type the printed code (K7QM-3FBR-9TZX). Same key exchange, same result. After connecting, the app shows a short daemon fingerprint; glance at it and confirm it matches the one in your terminal. The full story, including why that fingerprint matters, is on the Pairing a device page.
4. Open a session
In the codeout UI, create a session, point it at a working directory, and pick its mode.
In chat mode you message your agent and tap Allow or Deny when it wants to run a tool. In terminal mode you type as you would in any terminal. Either way the session keeps running on the daemon, so you can close the tab, walk away, and pick it back up from a different device with everything intact. That is the whole loop, and it works the same whether the agent is Claude, Codex, Gemini, or OpenRouter.
Next steps
New to chat mode? See Chat and terminal modes. Want to keep it off the internet? Remote access has the Tailscale path and local-only options. Running several sessions at once? That is Managing sessions.