How your machine stays in charge

The CommandChain app on your computer starts your coding agents for you. What an agent can do there is decided by the agent and by you, not by CommandChain.

The agent runs as you

When you start a session, the agent runs as your user, in the folder you chose, with its own permissions, configuration and limits. It uses the same sign-in and settings it uses when you run it in a terminal.

CommandChain adds no restrictions of its own and removes none: the agent’s own permission settings decide what it may do.

Full access is the one mode that skips the agent’s own permission prompts, and for Codex its sandbox too. Each agent names it in its own words, for example Full access (dangerously skip permissions) for Claude Code and Full access (YOLO) for Codex. The help text under the field says what it means for each agent:

Claude Code: “Bypasses Claude permission checks. The agent can use your computer’s files and commands without asking.”
Codex: “Bypasses Codex approval prompts and its sandbox. The agent can use your computer’s files, commands, and network without asking.”
GitHub Copilot: “Skips GitHub Copilot permission prompts. The agent can use your computer’s files, commands, and network without asking.” OpenCode and Cursor read the same, with their own names.

Your permission mode is the boundary

Each session has a permission mode, set under Security settings when you start it and in the session’s security panel later:

Auto approve: the agent’s tool requests are approved for you. Questions still wait for your answer. The New session form starts on this mode.
Ask for approval: every permission request appears in the conversation for you to approve or deny.
Full access: the agent’s own permission prompts are skipped, and its sandbox where it has one.

Not every agent offers every mode: Cursor offers only Full access and Auto approve. For an agent that offers it, use Ask for approval when you point it at a repository you do not know well. The details are in Choose agent permissions.

You approve every computer

A computer joins your account only when you approve it:

The computer shows a pairing code and its name. On the Connect a computer page, check that the Computer name and the code match what that computer shows before you approve.
A code works for 10 minutes. After that, get a new one by running the install command again on that computer, or commandchain-runner if CommandChain is already installed there.
Only a signed-in user can approve a code, and the computer belongs to the account that approved it. You see only the computers you approved.

If a code shows up that you did not start, deny it.

Removing a computer

To stop a computer from running sessions, uninstall the CommandChain app on it, as described in Update or uninstall. The computer then shows as Offline on Computers. Once it has been offline for 5 minutes, a workspace admin can take it off the list with Remove on its card. If you created your account yourself, you are its admin.

A removed computer can no longer connect to your account. To run sessions there again, it has to be connected with a new code that you approve.

If you no longer have the computer

If a computer is lost, stolen or out of reach, a workspace admin can still remove it from another device:

Open Computers and find its card.
Wait until it shows Offline and has been offline for 5 minutes. Until then, Remove is refused with “This computer was connected in the last 5 minutes. Try again after it has been offline for 5 minutes.”
Select Remove on its card, then Remove in the dialog.

See Remove a computer.

When you share a preview, anyone with the link can view it. Select Stop sharing to turn the link off. See Review artifacts and share previews.

Verified downloads

Both installers check the download against its published SHA256 checksum before anything is installed, and stop on a mismatch.

On macOS and Linux, a mismatch stops the install with this line (text in angle brackets is filled in by your computer):

checksum MISMATCH for <file>: the downloaded file is not the published one.

On Windows:

The download does not match its published checksum. Nothing was installed.