Caterm

CODEX & CLAUDE CODE SETUP

Your coding agent.
Your computer.

Caterm gives your locally installed Codex or Claude Code a browser workspace. The chosen device runs the agent with its existing login and project environment.

1. Prepare the device

Install and sign in to the Codex or Claude Code CLI on the computer where your project lives. On Mac, set its executable in Settings → Personal agent; the Files folder supplies the project root. For the Linux daemon, configure the executable and workspace before connecting.

The following paths are examples; replace them with real paths on your device.

export CATERM_CODEX_BINARY=/absolute/path/to/codex
export CATERM_CODEX_WORKSPACE=/absolute/path/to/projects
caterm connect --saved

Without an explicit executable path, the daemon searches trusted local CLI installation directories and its inherited PATH. The workspace defaults to the configured file root. Claude Code uses CATERM_CLAUDE_BINARY and CATERM_CLAUDE_WORKSPACE. A missing executable prevents conversation creation for that agent without disconnecting the device.

2. Create a conversation

  1. Open Chat and select New conversation.
  2. Enter a name, choose an online device, and select Codex or Claude Code.
  3. Choose a folder relative to the device's agent root. . uses the root; projects/example uses a subfolder.
  4. Create the conversation, then send your first prompt.

The device, agent, and project are fixed for that conversation. Create another conversation to change them.

3. Follow the work

Messages and tool activity stream into the browser. Review requested approvals, answer questions, or stop the current turn. Later turns resume the same native session on the same device. Activity links back to recent runs.

A browser disconnect does not stop a running turn: reconnect to replay its events. A daemon restart ends an interrupted turn; it is not automatically executed again.

Local execution and costs

Your Caterm plan covers the workspace and device access. It does not include model usage or replace your agent provider account. Each agent uses the login and configuration on the selected device. The Caterm server does not need a model API key for these conversations.

Agent permissions are local

The configured root limits the selected working directory. Agent tools follow the local CLI's permission policy; the scoped file browser is a separate boundary. Agents inherit the daemon’s OS identity, including root. Review execution approvals in the local CLI. Set CATERM_ALLOW_CODEX=false or CATERM_ALLOW_CLAUDE=false to disable the corresponding daemon adapter.

Learn about remote agent execution and permissions, or schedule repeatable workflows. Looking for collaboration? Share a device with another account →