OpenCode

OpenCode runs as a local agent in a pane and, on macOS and Linux, as a cloud or background agent. It is not an API-key agent: neither the local nor the cloud path takes a pasted key.

Local OpenCode

Coldtea does not manage OpenCode's login. OpenCode runs its own interface in the pane and owns its setup, including the /connect flow, model switching, and permission prompts. Sign in through OpenCode's own /connect inside the pane the same way you would outside Coldtea.

Coldtea only needs to find the opencode binary. If OpenCode does not appear in the agent picker, install the CLI and confirm it runs in your own terminal (see Connect agents).

Cloud OpenCode

There is no key to paste for OpenCode. Instead, Coldtea syncs your own OpenCode sign-in up to the cloud. It gets its own connect row in the cloud-run settings, separate from the API keys and Subscription options, so whichever credential source you picked for the other agents does not apply here. See Cloud agent credentials.

Choose a TeaHouse first, then Connect on the OpenCode row and sign in through OpenCode in the browser tab that opens. Coldtea notices when the sign-in lands and finishes on its own. If it has not caught up, tell it you have signed in and it checks again.

macOS and Linux only

Cloud OpenCode works on macOS and Linux. It is unavailable on Windows, where OpenCode runs under WSL and Coldtea cannot reach its sign-in from the Windows side. Local OpenCode panes still work on Windows.

Where to go next

• Connect agents for the local-versus-cloud picture across all agents.
• Cloud agent credentials for how the synced sign-in is stored per TeaHouse.
• Launch presets to set OpenCode's autonomy and model.
• Agent matrix for what each agent supports.