CLI
codeout is one command. Run it with no arguments and it starts the daemon in the current directory; add flags to change where it listens or how it is reached. This is a conceptual reference, so flag names describe intent rather than promising an exact string.
The command
Everything goes through codeout. With no flags it runs the daemon; flags like --pair or --install manage things without holding a session open. The working directory you run it from becomes the default working directory for sessions you open, which is why you usually run it from the project you care about.
Running the daemon
$ codeout opening tunnel (codeout.dev) ... ready Pair a device scan the QR, or type the code (QR prints here) address https://amber-cedar-204.codeout.dev code K7QM-3FBR-9TZX valid 5 min fingerprint 7Q3M-X2VD confirm this matches in the app
By default the daemon opens a public tunnel and prints that stable address plus a pairing secret, then holds the process open. Pass --local to skip the tunnel and stay on your network. Stop it with the usual interrupt, and its sessions stop with it.
Flags
<name>.codeout.dev for this machine. Same machine, same address every time, so a device you paired before still connects after a reboot. The daemon dials out, so no inbound port is opened. See Remote access.Restart=always, lingering enabled). Opens the tunnel by default; add --local for local-only. See Run on boot.--yes to skip.8400.The public tunnel is the default. It is still safe to leave open: over the tunnel the daemon accepts only paired-device tokens, and the device-to-daemon channel is end-to-end encrypted, so the tunnel carries sealed ciphertext it cannot read. The owner token and the plaintext path are local-only (LAN, Tailscale, this machine) and never work over the tunnel. A leaked tunnel URL reaches a locked door. Want nothing exposed at all? --local.
Run on boot
Install codeout as a background service so it survives closing the terminal and comes back after a reboot. Because it runs detached, you ask for the pairing details on demand with --pair.
$ codeout --install installed - codeout starts on boot with a public tunnel. $ codeout --pair scan the QR, or type the code, to add a device
After a reboot the daemon returns on the same address and reattaches your sessions, so paired devices reconnect on their own. Follow it with journalctl --user -u codeout -f; remove it with codeout --uninstall.
Adding and revoking devices
To add a device, run codeout --pair on the machine (or open Settings → Add a device in the app) for a one-time code, then enter it on the new device. Every paired device drives the same sessions.
To revoke one, open Settings in the app and revoke it. Revoking is immediate and surgical: that device's token is deleted on the daemon and any live connection is dropped on the spot, while every other device is untouched.
Environment
codeout runs your agents with the environment they already expect. Their API keys, model selection, and project config come from wherever those tools normally read them on the daemon host. codeout adds nothing to that environment and copies nothing out of it. If a flag and an environment setting disagree, the flag you typed on the command line wins for that run.
A couple of optional variables tune the daemon itself. CODEOUT_UPLOADS sets where chat uploads are stored on the host (default ~/.codeout/uploads); whatever you set, the daemon still pins it under your home directory. The Settings screen, when used, takes precedence over this variable.