dsh-zcode-cli-proxy: A Quota Proxy That Plugs the ZCode Client Agent into DeepSeek Harness

What Does It Do?

It is a DSH plugin for DeepSeek Harness that forwards the harness's model requests to the agent bundled with the local ZCode client. It solves the problem of using ZCode quota without an API key or a self-hosted gateway: the plugin injects a Start Plan account over a persistent app-server channel and returns OAuth credentials before each request, so usage is billed directly against your ZCode Start Plan / Coding Plan quota. It is maintained by kyle123740 under the AGPL-3.0 license and was last updated on 2026-10-01.

Core Features

• Persistent app-server channel: launches the ZCode app-server the same way the GUI does, reusing one session per DSH sessionId so multi-turn conversations work without any API key.
• True streaming and multimodal input: text and reasoning deltas are forwarded as they arrive, tool calls are supported, and images are attached as local files for the agent to read.
• Turn-lock self-healing: when a turn is already running it sends a stop, waits, and retries; if a session is gone it creates a new one and replays the conversation, and it invalidates mappings when the process exits.
• Quota and auth injection: injects the Start Plan account and returns the shared credential before each request so the agent can sign its own calls.
• Configurable behavior: master switch, CLI path and node executable, model list, working directory, credential directory, and per-request and per-turn timeouts are all adjustable.

How to Use This Plugin?

In DSH settings, open the Models page and pick the "ZCode Start Plan (client proxy)" provider with its model; from then on the harness's model requests run through the persistent ZCode app-server. Your machine needs the ZCode client installed and signed in with an account that has Start Plan quota, and the plugin auto-detects the bundled script path. Auxiliary calls such as session titles are generated locally and consume no quota; to change behavior, adjust the working directory, model list, or timeouts under Settings → Plugins.

How to Troubleshoot This Plugin?

A "turn failed · PROVIDER" message usually means the previous turn was aborted or timed out and the turn lock was not released; the channel layer sends a stop and retries automatically, so manual intervention is rarely needed. If the session is reported as missing, it was recycled or the process restarted, and the plugin discards the cached entry, creates a new session, and replays the whole conversation. If quota is still not hit after account injection, check that the revision identifier matches the config source character for character, since a mismatch is skipped silently; auth must also use a valid token from the shared credential, as returning an expired one makes the upstream reject the request.