FAQ

Short answers, no hedging. If something here raises a follow-up, the linked pages have the long version.

Is there really no relay or cloud?

None. codeout has no servers. Your devices connect straight to your daemon. There is no account to create and no company sitting in the path of your sessions. Even when you use the default public tunnel, it forwards encrypted bytes; it is not a relay that can read them.

Does it work without internet?

Yes. On a LAN with no internet at all, a paired device reaches the daemon and runs sessions normally. Internet only matters when you want to reach the daemon from outside its network, and even then you bring the path. The daemon does not phone home to function.

Which agents are supported?

Claude, Codex, Gemini, and OpenRouter (supporting any model such as Claude 3.7 Sonnet, DeepSeek R1, GPT-4o, and Llama 3.3 with native tool execution), in chat mode and terminal mode. Install any mix, pick per session, or configure credentials in the Host Control Deck (http://localhost:8400/). A plain shell works too, with no agent at all.

Can I send files or images?

Yes. In chat mode, tap the attach button and pick files or images, up to 100 MB each. They upload to a folder on the daemon host (~/.codeout/uploads by default, changeable in Settings) and never leave your machine. The agent reads them back without a permission prompt, since they are your own uploads. Images open in a full-screen lightbox, and tapping any file downloads it. See Chat and terminal modes.

What is the difference between chat mode and terminal mode?

Chat mode is a messaging UI over your agent: streamed replies, thinking/reasoning traces, markdown, collapsible tool cards, slash commands, and a tap to Allow or Deny each tool. Terminal mode is the raw PTY, for full-screen TUIs and plain shell work. You pick per session. See Chat and terminal modes.

Does the agent run commands without asking?

No, not in chat mode. When the agent wants to use a tool, it pauses and asks; you tap Allow once, Allow for session, or Deny. Obvious read-only calls are auto-allowed so you are not approving every file read, but anything that would have prompted in a normal terminal reaches you instead.

Where do my API keys and credentials live?

On the daemon host, in your local config (~/.codeout/config.json, mode 0600) or existing CLI configs. Manage them via the Host Control Deck on http://localhost:8400/. Keys never leave the machine the daemon runs on, and they never reach your phone or client devices.

Can two devices use the same session at once?

Yes. The session lives on the daemon, so multiple paired devices can attach to it and see the same live session. In chat mode each device has its own name, colour, and avatar, so messages are attributed and colour-coded per device. Detaching one does not disturb the others. Handy for starting on a phone and finishing on a desktop without dropping a beat.

A device was lost. Now what?

From any paired device, open Settings and revoke it. It can no longer connect or decrypt new traffic. Then rotate any secrets it could have displayed on screen, the same as you would after losing any logged-in device. The token is per-device, so revoking it costs you nothing on your other devices.

Is the public tunnel safe to use?

Yes, and it is more private than opening a port. The daemon dials out, so your home IP is never exposed; the public only ever sees Cloudflare. The channel is encrypted end to end, so the tunnel carries sealed ciphertext and reads nothing. You still pair against the public address with the same QR or code and confirm the same fingerprint, so an impostor in the path is caught.

What is the license?

MIT. Read every line, host it yourself, and send pull requests. The source is on GitHub. If you do not trust a tool with your terminal, the right move is to read it, and this one is built to be read.