[ShayNeeo]

Summary

Following #4842 (which updated OpenCodeExecutor in open-sse/executors/opencode.js and open-sse/utils/opencodeFingerprint.js for the OpenCode v2 3-layer free-tier gate), OpenCodeZenExecutor (open-sse/executors/opencode-zen.js, ocz/*) only received the generateSessionId/translateSessionId counter update and still sent:

1. OPENCODE_UA = "opencode/1.18.31" and v1 hasValidOpencodeVersion (>= 1.17)
2. x-opencode-client: "desktop" and only x-opencode-session (omitting x-opencode-session-id, x-session-affinity, x-session-id, and x-opencode-project)
3. Local ensureChatFingerprintTools / ensureResponsesFingerprintTools helpers injecting ["bash", "glob", "grep", "read"] with empty parameters: { type: "object", properties: {} }

Live Upstream Verification

Even when authenticated with a Zen API key on /zen/v1/*, upstream evaluates the free-tier gate on free models (ocz/space-bunny-free, ocz/mimo-v2.6-flash-free, ocz/muse-spark-1.3-contributor-free, ocz/big-pickle, and tests/translator/real/opencode-zen-free-responses.real.test.js) before validating the API key:

• OpenCodeZenExecutor before this commit (opencode/1.18.31 + properties: {} stubs): HTTP 403 FreeTierError
• OpenCodeZenExecutor with v2 headers + old properties: {} stubs: HTTP 403 FreeTierError
• OpenCodeZenExecutor with v2 headers + applyFingerprintTools(out, flat) (read/shell verbatim schemas): passes the 403 FreeTierError gate completely.

Changes

• open-sse/executors/opencode-zen.js:
  • Align OPENCODE_UA ("opencode/latest/2.0.26/cli"), OPENCODE_CLIENT ("cli"), and hasValidOpencodeVersion (v2 channel/version/client regex) with open-sse/executors/opencode.js.
  • Send mirrored session headers (x-opencode-session, x-opencode-session-id, x-session-affinity, x-session-id) and x-opencode-project in buildHeaders.
  • Replace duplicate ensureChatFingerprintTools / ensureResponsesFingerprintTools stubs with shared applyFingerprintTools(out, false) / applyFingerprintTools(out, true) from ../utils/opencodeFingerprint.js (including caller tool conflict aliasing and placeholder system/instructions note).
• tests/unit/opencode-session.test.js:
  • Add unit tests verifying OpenCodeZenExecutor v2 headers and read/shell fingerprint application on Chat Completions and Responses requests.

Note: Built atop the #4842 commits (d8d0e04c, ccfb7838) so the top commit (cb825c7) cherry-picks cleanly onto local master.

Refs #4845, #4842, #4837, #4839

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[AFG473319]

Thanks for this ??? it fixed OpenCode Zen free-tier 403s for us too. ????

We've backported it into our fork (AFRouter), adapted to our diverged opencode-zen executor:

??? AFG473319/AFRouter#53

Notes from our reproduction, in case they're useful to you:

• The original shape (opencode/1.18.31 UA, desktop, bash/glob/grep/read, no x-opencode-project, no session mirrors) returned 403 FreeTierError against https://opencode.ai/zen/v1/chat/completions for mimo-v2.6-flash-free ??? both with a keyed Bearer sk-??? and with Bearer public.
• Adding x-opencode-project + the mirrored session headers to that same old body flipped it to 200 in our live probes, which is exactly the header change you made here.
• One caveat for anyone re-testing: after a burst of probes the gate started answering 429 FreeUsageLimitError and then a blanket 403 FreeTierError for every shape (including this fix's fingerprint), so the limiter appears per-IP/abuse-based, not purely fingerprint-based.

Full credit to @ShayNeeo in our commit (Co-authored-by) and PR body. Thanks again! ????

[luqman-v1]

LGTM: aligns OpenCode Zen free-tier v2 headers and read/shell tool fingerprint. Safe and clean.