OpenCode Integration Guide

Overview

OpenCode is an open-source coding agent available as terminal, desktop, or IDE extension. Cup’n’String governs it through process detection, provider/API proxying, MCP controls, and local-service policy.

Support level

Compatibility Adapter + MCP/provider proxy support

What Cup’n’String detects

• OpenCode process/app where installed
• Workspace/session path
• Provider endpoints
• MCP or custom agent configuration where available

What it governs

• Provider/API traffic
• MCP tools
• Local services
• Secret exposure

Recommended policies

• Require approved provider proxy
• Audit session activity
• Restrict local service and container access

Setup outline

1. Ensure the Cup’n’String daemon is active.
2. Configure OpenCode proxy parameters to map through the local proxy gateway.
3. Establish provider domain mapping configuration.

Verification

Confirm that model request calls originating from OpenCode are intercepted and audited.

Troubleshooting

If process detection fails, check if OpenCode is run under a non-standard name or custom container.

Known limitations

Support depth depends on OpenCode mode: terminal, desktop, or IDE extension.