use-opencode-local-provider

OpenCode Zen models are capable, yet dsh does not expose them as a native provider out of the box, so wiring them up usually means rolling your own forwarding layer. This plugin removes that friction: install it and the full OpenCode Zen catalog appears in the dsh chat UI immediately.

Under the hood, the plugin ensures an opencode serve instance is running on load, then spins up a lightweight OpenAI-compatible bridge that maps /v1/chat/completions requests into opencode sessions over the local HTTP API. The flow travels through the opencode client channel, meaning no OpenCode API key is needed and public /zen/v1 quota stays untouched. Crucially, the bridge preserves opencode's native tool calls and connected MCP servers, letting the model decide when to invoke them inside its own sandbox, while dsh simply receives the final chat completion and stays out of the tool-orchestration loop.

Ideal for developers who already have opencode installed and want to drop the OpenCode Zen model family directly into their dsh interface—without extra API keys or public quota consumption. Configuration covers server and bridge ports, working directory, stream timeout, and an automatic permission-reply policy (once, always, or reject), so sensible defaults get you running right out of the box.