Skip to content

opencode-zen-big-pickle.md

Latest commit

 

History

History
89 lines (69 loc) · 4.86 KB

opencode-zen-big-pickle.md

File metadata and controls

89 lines (69 loc) · 4.86 KB
Raw

OpenCode Zen + Big Pickle Model Configuration

Big Pickle is a free stealth model available on OpenCode Zen during its beta period. It uses the Chat Completions API exclusively.

Compatibility Matrix

Tool Version Works? Notes
Codex CLI v0.93.0 Yes Last version with wire_api = "chat"
Codex CLI v0.118.0+ No Removed chat completions support
OpenCode CLI v1.4.3 Yes Pipe empty stdin in non-TTY: echo "" | opencode run --pure "msg"
Direct curl - Yes POST to /v1/chat/completions

Config Recipes

Codex CLI (~/.codex/config.toml)

[model_providers.opencode-zen]
name = "OpenCode Zen"
base_url = "https://opencode.ai/zen/v1"
env_key = "OPENCODE_ZEN_API_KEY"
wire_api = "chat"

[profiles.pickle]
model = "big-pickle"
model_provider = "opencode-zen"

OpenCode CLI (~/.config/opencode/opencode.json)

{
  "$schema": "https://opencode.ai/config.json",
  "model": "opencode/big-pickle",
  "provider": {
    "opencode": {
      "options": { "apiKey": "sk-..." }
    }
  }
}

Gotchas

  • Big Pickle only supports /v1/chat/completions, NOT /v1/responses
  • opencode run hangs without piped stdin in headless environments
  • Codex CLI deprecation warning for wire_api = "chat" is safe to ignore on v0.93.0
  • In Codex Web Local's Zen proxy, DeepSeek thinking-mode responses must round-trip reasoning_content into later Chat Completions messages. Missing this field can produce The reasoning_content in the thinking mode must be passed back to the API.
  • Chat-shaped Zen proxy payloads must be posted to /v1/chat/completions, even when the incoming local request uses the Responses-shaped /responses route.

Codex Web Local Proxy Behavior

Codex Web Local can expose OpenCode Zen through its local Responses-compatible proxy. The proxy translates between Codex-style Responses input and Zen's Chat Completions-only API.

For thinking-mode models behind big-pickle, the proxy must preserve assistant reasoning in both directions:

  • Upstream Chat message.reasoning_content becomes a Responses reasoning output item with summary_text and content: [], so later Responses-backed turns do not replay non-empty reasoning content and trigger array_above_max_length.
  • Later Responses reasoning input becomes assistant Chat reasoning_content.
  • Reasoning that precedes function calls is attached to the assistant tool-call message.
  • Streaming Chat reasoning_content deltas are emitted as synthetic Responses reasoning output.

This behavior was fixed in commit 47d52c8c after a Docker repro using an empty CODEX_HOME, no login, and no Zen API key.

Provider-Scoped Composer Model Behavior

When Codex Web Local is running in free-mode provider workflows, the visible composer model is the model that must be sent for the next turn. Backend thread/resume, free-mode status, provider defaults, and per-thread provider choices can all report model state, but the send path must use the currently visible provider-scoped composer model.

The provider/thread scoping fix landed across commits dc7871a8, 28f76372, and 6ecfed96:

  • The composer submit payload includes the visible selected model.
  • The selected model override is passed through App.vue into sendMessageToSelectedThread().
  • turn/start uses that selected model override instead of allowing a resumed backend model from another provider to replace it.
  • Free-mode status hydrates the provider-scoped model after startup and provider switches.
  • Provider switching preserves existing per-thread/per-provider model selections and only seeds a thread from the provider default when no thread/provider model exists.
  • Free-mode status fetches are bounded with an 8 second timeout.

The validated provider-switch flow was:

Thread Provider Composer model Sent model Received reply
019e0aef-f2ca-7d61-8345-efd4aac9ea7b OpenRouter openrouter/free openrouter/free Yes
019e0d1c-41e0-7670-a55a-664fe46f80a8 OpenCode Zen big-pickle big-pickle Yes
019dc7fa-5291-7670-8b9b-d06ae0548d01 OpenCode Zen big-pickle big-pickle Yes

The browser verification clicked send and waited for an assistant message row containing the exact marker, not only for the outgoing /codex-api/rpc turn/start payload.

Related