web-search-opencode-responses

Configuration

The plugin registers a settings section (web-search-opencode-responses) on the Host. Note: the dsh web Plugin configuration tab only shows cards for the provider namespaces the web client ships (DeepSeek, Shell, Agent loop) — a third-party namespace like this one has no client card yet, so configure it through the settings document instead:

• key — visual: dsh web Settings → Models, write the OPENCODE_GO_API_KEY credential (stored in ~/.dsh/.credentials.yaml).

• endpoint / model / key reference — edit the settings document ~/.dsh/settings.yaml, opened in the web UI by the Open configuration file button:

  web-search-opencode-responses:
    baseURL: https://opencode.ai/zen/go/v1   # optional; /responses is appended
    model: deepseek-v4-flash                  # optional; server-side search model
    apiKeyEnv: OPENCODE_GO_API_KEY            # optional; credential reference
    apiKey: ""                                # optional; literal key over the ref
  

  The file hot-reloads, so a change applies on the next search; the provider reads the section per search, no restart needed.

Equivalent static values can be authored in the plugin's cordis.patch.yml entry (the composition base); the settings document overrides it. See the Configuration field table below:

field	default	meaning
apiKey	–	literal key; prefer the credential store
apiKeyEnv	OPENCODE_GO_API_KEY	credential reference resolved per search
baseURL	https://opencode.ai/zen/go/v1	gateway endpoint; /responses appended
model	deepseek-v4-flash	Responses model with server-side search

The key resolves through dsh's credentials service first (the web Models page writes ~/.dsh/.credentials.yaml), then the launching environment; a stored secret never leaves the machine — the wire surface redacts it.