DSH PRO
Download
Back to DSH PRO

Safe use

Using DSH PRO safely

Effective 24 August 2026

DSH PRO gives an AI agent real access to your Mac. That is what makes it useful, and it is the thing to understand before you run it. This page is the honest account of what the agent can reach, where the limits are, and how you stay in control.

What the agent can do

Inside DSH PRO the agent does not just answer. It acts. Here is what it can do.

  • run shell commands on your machine.
  • read and write files inside the workspace folder you choose.
  • spawn subprocesses.
  • in Dispatch mode, drive other CLI coding agents you have installed as headless subprocesses, handing work from one session to another.

The workspace folder you pick is the scope for the agent's file edits. Its shell commands and subprocesses, though, run under your own user account, so treat the agent's reach as roughly your own reach at a terminal. Point it at a folder you are comfortable giving it, and remember a command can do more than edit a file.

The local API has no auth

To talk to its own interface, the app runs a small HTTP API on your machine. That API has no authentication. Any process already running on your Mac could reach the running agent through it and drive it.

This is a deliberate, accepted tradeoff. For single-user local use — one person, on their own machine — it is fine, and it keeps the app simple with nothing to log into. It stops being fine the moment that API is reachable by something you do not trust.

So do not expose it. Do not forward its port, do not put it behind a tunnel or reverse proxy, and do not run DSH PRO on a shared or multi-user machine where a process you do not control could reach it. Keep it local.

Review before you run

An agent with shell and file access can do destructive things — delete files, overwrite hours of work, run a command with consequences you did not foresee. Most of the time it does exactly what you asked. The cost of the exceptions lands on you, so build the habit of watching.

  • Read what the agent proposes before you let it run, especially anything that deletes, overwrites, moves files, or reaches outside the folder you meant.
  • Keep work that matters under version control or backup, so a bad step is a revert and not a loss.
  • Be extra deliberate with destructive or irreversible actions. When in doubt, stop it and look.

You are responsible for what the agent does on your behalf. Review is not optional politeness. It is how you stay in control of a tool that can act on its own.

Sign-in and vendor terms

Sign-in uses OAuth, and it uses each vendor's own CLI OAuth client rather than one of ours. That is why the consent screen names that vendor's client — the Codex CLI, for example — and not DSH PRO. It is deliberate and disclosed. Those client IDs belong to the vendors. They can change or revoke them at any time, and if a vendor does, that sign-in path stops working until it is updated.

Connect only accounts and keys that are yours, and use them within the terms of the subscription behind them. Some providers place limits on automated use or third-party clients. Whether a given subscription may be used this way is between you and that provider, not something DSH PRO can grant you.

Your credentials are stored locally, as plaintext YAML at ~/.dsh/.credentials.yaml with 0600 file permissions. They are sent only to the provider you authenticate with. They are never sent to us — there is no server of ours for them to go to.

Acceptable use

Do not use DSH PRO, or the agent inside it, for any of the following.

  • do anything unlawful, or have the agent carry out something unlawful on your behalf.
  • attack, probe, or gain access to systems, networks, or accounts you do not own or are not authorized to test.
  • access, copy, or move data you have no right to.
  • break the terms of the AI subscriptions or other services you connect to it.
  • build or distribute malware, or automate spam, fraud, or abuse.

The tool does real work on real systems. Point it at your own.

No warranty

DSH PRO is provided as is, without warranty of any kind. It is a desktop shell over the DeepSeek Harness npm packages, which are MIT licensed and redistributed under that license. The same as-is, no-warranty spirit applies to the whole app.

Running an autonomous agent with shell and file access carries real risk, and by running it you accept that risk. To the extent the law allows, ByteForward is not liable for what the agent does, for lost or damaged data, or for how the third-party services you connect respond to it.

DSH PRO is not affiliated with, endorsed by, or an official release of DeepSeek or DeepSeek Harness.

Reporting a problem

Found a security issue, or something behaving in a way this page did not prepare you for? Tell us. The contact point is the ByteForward YouTube channel — @ByteForward — reach out there and we will follow up.

There is no data-collection backend behind DSH PRO and no account system, so there is nothing to file a data request against. If a report involves your credentials, remember they live only on your own Mac, at ~/.dsh/.credentials.yaml.