dsh-opencode-freeaccess
为 opencode 提供 dsh 会话 ID，无需配置。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:mubaid/dsh-opencode-freeaccess#7411d97ab2b4ef526a06ad352b52834e9f7e11a9Opencode Freeaccess 以 dsh-opencode-freeaccess 发布，当前版本为 0.2.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Use OpenCode's free models in DeepSeek Harness. No proxy, no paid key, no config.
English | 简体中文
You point a DeepSeek Harness provider at opencode.ai, pick one of their free
models, and send a message. It fails:
403 FreeTierError: OpenCode's free tier can only be used from within OpenCode
Nothing is wrong with your key, your model id, or your harness. OpenCode serves its free tier only to requests that carry a session id, and dsh does not put one on the wire.
Your realistic options are all worse than the fix:
One plugin puts the session id on the request. That is the whole job.
dsh plugin --profile web add github:mubaid/dsh-opencode-freeaccess
Restart the profile. OpenCode's free models now work in dsh.
Before:
opencode2 / space-bunny-free
> 403 FreeTierError: OpenCode's free tier can only be used from within OpenCode
After the install line above, same provider, same model, same key:
opencode2 / space-bunny-free
> streaming normally
No new provider block. No gateway. No per-request anything.
It targets the real gap, not a symptom. dsh already knows the session id. The adapter simply never forwards it. This closes that gap at the only layer that can reach the wire, so you inherit the behaviour instead of rebuilding it.
One conversation, one stable id. The id is derived from the conversation's birth time and its uuid, so it survives a restart and is identical afterwards. Conversations running at the same time never share an id.
It cannot change your output. Only request headers are added. Body, URL, method, credentials and response pass through untouched, and requests to any other host are forwarded with their exact original arguments. There is a test that diffs a matched request against an untouched control and asserts the headers are the only difference.
It works with whatever route you already have. A direct opencode.ai
provider, or your own gateway or proxy. Point baseURLs at it.
verbose: true logs every id it sends.dsh plugin --profile web add github:mubaid/dsh-opencode-freeaccess
systemctl restart dsh-web
That is the whole setup. Defaults match opencode.ai and the standard routes.
To see it working:
journalctl -u dsh-web -f | grep opencode-freeaccess
A long agentic session. The conversation id stays constant for the whole run, so upstream can keep one prompt cache warm instead of rebuilding it.
Parallel subagents. Fan out ten subagents. Each carries its own id and none contaminates the others.
Self-hosted only. If you would rather not hand traffic to an aggregator, this keeps the path from dsh to OpenCode direct, with the free tier intact.
Migrating off a proxy. Drop the proxy hop and keep the models.
The header set, in full:
| Header | Purpose |
|---|---|
x-opencode-session | The session header the OpenCode gateway keys on |
x-session-affinity | Affinity family, for cache and routing |
x-opencode-session-id | Companion session header the official client sends |
x-session-id | Companion affinity header |
x-opencode-client: cli | Client fingerprint |
x-opencode-project: global | Project fingerprint the official client sends |
User-Agent: opencode/latest/<version>/cli | Client fingerprint |
The id format is OpenCode's own: ses_, then 12 hex characters derived from the
conversation's creation time, then 14 characters derived from the conversation
uuid. One dsh conversation maps to exactly one id, for its whole life.
Everything is configurable from the profile's patch layer under the id
opencode-freeaccess: providers, hosts, baseURLs, headers,
extraHeaders, userAgent, sessionIdEnv, verbose, seedSessionId,
disableFetchInjection. Defaults are documented in
docs/design.md.
Implementation notes, the test suite, and an explicit list of what has not been verified are in VERIFICATION.md.
| OpenCode CLI | Proxy or aggregator | This plugin | |
|---|---|---|---|
| Harness | OpenCode only | Any | DeepSeek Harness |
| Free tier | Yes | Depends on the provider | Yes |
| Extra hop | No | Yes | No |
| Infrastructure to maintain | None | Some | None |
| Subagents and parallel sessions | Yes | Yes | Yes |
Early, and honest about it. A small plugin with a narrow, well-defined job.
0.2.0-rc.2 and 0.2.1-alpha.4
(engines.dsh: ^0.2.0-rc.2).fetch-based protocols: openai-completions, openai-responses,
anthropic-messages.fetch and are not supported.read tool to be present in the request
(the official client sends read + shell). dsh ships a tool with exactly
that name, so this holds by default, but disabling it will make the gateway
reject the request.Issues and pull requests are welcome. If you are adding behaviour, please add a test with it and keep the headers-only guarantee intact.
MIT. See LICENSE.