OpenCode
Run OpenCode with any model provider you choose, inside governed Proliferate workspaces.
OpenCode is the most provider-flexible agent Proliferate runs. Other agents authenticate against one provider; OpenCode fronts more than a hundred at once, so a team with a preferred or niche model can plug it straight in.
Supported functionality
| Capability | Support |
|---|---|
| Repository workspaces | Run OpenCode in a local checkout or a worktree. Cloud workspaces are coming soon. |
| Provider flexibility | Bring keys for OpenAI, Anthropic, Gemini, OpenCode Zen, or providers from Proliferate's vendored list; native providers and several added keys can coexist. |
| Modes | Switch between OpenCode's own build and plan modes from the composer. |
| Review | Inspect generated diffs, the transcript, and command output before merge. |
| Credentials | OpenCode's existing provider auth stays active. Keys you add under Providers apply alongside it. |
Modes
| Mode | What it does |
|---|---|
| Build | Default. Makes changes directly: edits files and runs commands as it works. |
| Plan | OpenCode's own plan mode: it works out an approach before making changes, using OpenCode's native planning behavior. |
Authenticate OpenCode
Settings -> Agents -> OpenCode looks different from the other agents: instead
of method cards it shows a Providers section, with an icon for each
provider you've configured and a Configure button. Keys you add are wired
into OpenCode alongside its own CLI logins from opencode auth login, which
always stay active.
Configure opens a searchable list of Proliferate's vendored providers. Expand a provider and paste its key: the key is saved to your vault and wired into the provider's usual environment variable for you. A configured provider shows that variable with a redacted hint and can be replaced or removed. Proliferate does not show an Authenticate action for OpenCode.
An admin can restrict which managed routes members may newly configure. See Agent policy.
For routes, BYOK, and gateway details shared across harnesses, see Authentication.