FAQ

No. It is the interface and control layer for those CLIs. You keep your existing provider access, your local tools, your configuration, and your model choices. Termdeck drives the official CLI unmodified.

Cloud agents run on someone else's infrastructure against a copy of your repository. Termdeck runs the agent on machines you own, so it uses your actual checkout, your running services, your environment variables, your credentials, and your MCP servers. Nothing has to be synced anywhere, and there is no environment to reproduce.

Yes. Termdeck reads and writes the same session files the CLIs do, so claude --resume and codex resume pick up a chat you drove from the browser. Chats started in a terminal appear in the browser the same way.

Yes. Connect macOS, Linux, and Windows machines and see all of their chats on one board: a laptop, a desktop, a VM, a home server, a remote development box. Free connects one machine, Starter two, Pro ten.

No. The agent dials out over HTTPS and keeps that connection open. Nothing listens for inbound traffic, so a machine behind NAT, on hotel wifi, or inside a corporate network works with no configuration.

There is no separate server for you to run, and the parts that must be local already are: the agent, the CLI, your credentials, your repository, and your transcripts. The hosted master holds an account, a machine list, and preferences. Adding a local server would only move the web app, which is the one piece that holds nothing.

No. Turns run under your own Claude, ChatGPT, or SuperGrok subscription and bill to that provider. Termdeck charges for the control plane and never resells model access.

One machine, one session at a time, 30 browser started turns a month, and unlimited reading, approving, denying, stopping, and notifications. The intent is that a free account can always watch its agents and unblock one that is waiting.

The account drops to Free automatically. Nothing is deleted: machines stay registered, rules stay saved but paused, and every chat stays where it is. No card is asked for at any point during the trial.

A fixed list of typed operations: read and watch transcript files, read files inside an open chat's project folder, start one of the three known engines and relay its input and output, report machine facts, restore a checkpoint the engine itself made, edit the project instruction file, and switch a saved account. There is no capability that runs a command of the caller's choosing. Security and privacy has the full account.

Yes, and the installer offers to print all of it before it touches anything. You can also fetch the same files directly at any time from /download/agent/.

Only what you open. Transcripts stream when you open a chat, and file contents and diffs stream when you open them in the dock, both to your own browser. Termdeck stores neither. Repository content you have not opened never crosses the wire.

No. Each CLI stores its own credentials on your machine. Termdeck reads whether a login exists, never the secret. Rate limits are read locally against the provider and only the percentages are sent.

Yes, on the same machine or different ones. A common split is a premium subscription on hard problems and a cheaper engine on routine work, with the usage page showing whether it is paying off.

Yes on Claude and Codex. Connect each login, watch their limits side by side, and switch in one click when one runs out. The chat keeps going under the account you switched to. Grok account switching is done with grok login on the machine.

Because that engine cannot honour it. Termdeck does not show a control that would quietly mean something different, and where an engine interprets a mode differently the caveat is printed under the picker.

The run keeps going. The agent holds the process alive across a dead link and replays what you missed when you return. Same for losing wifi, sleeping a laptop, or a Termdeck release.

Another process is attached to that session, usually a terminal running the CLI on the same chat. Two writers would fork the transcript, so Termdeck goes read only instead. It unlocks itself when the other process lets go.

Yes, including straight from the notification. On iOS, add Termdeck to your home screen first: Safari only allows web push for an installed site.

Check Archive, and check that the project folder is added in Settings, then Projects. Termdeck never deletes a transcript: they belong to the CLI and live on your disk.

No. Your browser talks to the hosted master and the master talks to your machine, so both need a connection. Work already on disk is unaffected and the CLI keeps working in a terminal.