Enable computer use in DeepSeek Harness: DSH plugin setup

computer use lets a DeepSeek Harness agent drive the graphical interface directly — simulating clicks, typing on the keyboard, and reading screenshots, rather than only running tools on the command line (source). This guide covers three things: how it divides work with browser control and built-in tools, how to enable and configure it, and the permission and safety boundaries you must observe.

What computer use is: letting a DeepSeek Harness agent drive the GUI

computer use is the class of capability that lets a DeepSeek Harness agent drive the graphical interface directly: simulating clicks, typing on the keyboard, and reading screenshots to operate arbitrary desktop software. Ordinary built-in tools are the framework's general-purpose set, able to read and write files, run commands, and search the web; computer use carves out "operating the computer itself" at the OS level. The three divide work like this:

1. Built-in tools — general tools the model can call, such as reading and writing files, running commands, and searching the web. Expected: they cover most software-engineering tasks without touching the GUI.
2. Browser control — open pages, scrape, interact, and screenshot only within the browser process. Expected: it specializes in web automation with a narrower permission surface.
3. computer use — control the mouse and keyboard and read the screen, able to drive any window. Expected: it covers local apps and cross-application flows that the browser cannot reach.

In one sentence: browser control works "inside one window", computer use works "across the whole machine" — more capable, at the price of wider permissions.

Enable computer use in DeepSeek Harness: built-in switch or DSH plugin

There are two routes to enabling computer use: install a DSH plugin that provides the capability, or enable the built-in tool chain in a supported profile per the official docs. Because it drives the graphical interface, it needs wider sandbox authorization than ordinary tools and is normally not enabled in the default least-privilege profile. On the plugin route:

1. Install the plugin — run in your terminal:
   bash

   dsh plugin --profile web add dsh-computer-use
   

   Expected: the terminal echoes that the plugin joined the web profile.
2. Relax sandbox authorization — confirm the current profile's sandbox mode permits interface-level actions. Expected: the agent can drive the mouse and keyboard instead of being blocked by the gate.
3. Restart to take effect — restart DeepSeek Harness as prompted so the capability enters the config tree. Expected: a new session can invoke the capability.
4. Verify on a small scope — first have it do one clear, harmless action, such as opening a notepad and typing text. Expected: the action visibly happens, proving the chain works.
5. Turn it off when done — switch back to a restricted profile once the task ends. Expected: the permission surface is reclaimed, lowering the risk of mistakes.

If you prefer not to use the command line, browse the computer-control / automation category on DSH Plugin Hub for a computer-use plugin and install one by compatibility status.

computer use safety boundaries: DSH plugin authorization scope and escalation risk

The risk of computer use comes from it naturally crossing the sandbox boundary: the screen, clipboard, and credentials can all be exposed to the agent, amplifying the consequences of mistakes and malicious prompts. The DeepSeek Harness sandbox can constrain a subprocess's file effects (source), but OS-level mouse and keyboard control is not covered, so restraint matters. Three boundaries:

1. Keep authorization minimal — enable it only where you genuinely need desktop operation, never leave it on permanently. Expected: the exposure window is minimized.
2. Avoid sensitive screens — do not let it touch banking, password managers, or terminals holding keys while it is on. Expected: credentials stay out of model context.
3. Plan for prompt injection — malicious instructions in pages or documents can induce it to act. Expected: critical actions keep human confirmation.

DSH plugin configuration notes

1. Confirm the profile first: install into the profile you are actually using (such as web), or it will not take effect.
2. Coverage differs by OS: Windows, macOS, and Linux support interface control differently; read the plugin description first.
3. Escalation is a policy problem: installing the plugin is not enough — the permission policy and sandbox mode are the real boundary.
4. If it does nothing, read the log first: separate "not installed properly" from "blocked by the gate" instead of blindly reinstalling.
5. Do not stack permissions with a browser plugin: if you only automate the web, use a browser-class plugin for a narrower surface.

Sources: dsh-computer-use (DSH Plugin Hub), process sandbox (DeepSeek Harness docs), tools subsystem (DeepSeek Harness docs).