DeepSeek Harness

One command adds the OpenCode Console plugin to DeepSeek Harness (dsh) on your computer and connects it to a workspace. You keep using the Web UI (dsh web), dsh headless, ACP and the SDK as before, with these changes:

• The model picker lists the workspace's models, including ones from other providers, and new sessions start on the newest Claude Sonnet the workspace offers. Requests go through Console, so the workspace's model rules and budgets apply.
• The workspace's Providers rules apply to every model request, DeepSeek's own models included. A request to a provider they block is stopped.
• Every tool call, and every /name skill in your messages, is checked against the workspace's policies before it runs or asks for approval.
• The workspace's MCP servers are added, with OpenCode Web Search when the workspace offers it.
• The workspace's Library skills are added to ~/.dsh/skills, so you can run each one as /name. Its Library instructions are added to the system prompt.

DeepSeek Harness checks Console for changes every minute. The Web UI applies them right away, and other profiles the next time they start.

• An OpenCode Console workspace you're a member of.
• DeepSeek Harness 0.2.2-rc.1, a developer preview. A later release may change what setup relies on.
• Node.js 22 or later, for npx.

1. Run this in a terminal:
   npx @opencode/console setup deepseek-harness
2. Your browser opens Console. Check that the code matches the one in your terminal, approve the sign-in and pick the workspace.
3. Setup prints the models, policies, MCP servers and Library items it set up. Run dsh web, or restart it if it's running.

Run the command again any time to update the setup. If the workspace offers no models, DeepSeek Harness keeps its own providers and still gets the workspace's policies, MCP servers and Library.

To see who you're signed in as, the workspace, and how many policies and models it has, run:

To undo setup, run:

It takes setup's block out of cordis.patch.yml, leaving the rest of the file as it was, and deletes the workspace's skills. Your own model providers come back. You stay signed in until you run npx @opencode/console logout.

• While it's connected, the workspace's models replace the model providers your profiles set. Setup names the profiles this affects.
• The Web UI can't save a new default model or changes on its Models page, since setup sets them. You can still pick a model for each session.
• Policies are checked by the plugin, so they hold only while setup's block is in place. Plugins you install and patches you pass with dsh --patch aren't checked. Tools that run code Console can't read, such as run_code and the terminal tools, are blocked while the workspace's policies limit shell commands.
• Until DeepSeek Harness has the workspace's policies, it blocks every tool call, and it runs no agent if the plugin can't load. If Console can't be reached, the policies it last fetched stay in place.
• If ~/.dsh/cordis.patch.yml already sets model providers or a default model, setup keeps yours and doesn't add the workspace's.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays). The support page covers data requests, security reports and more.