DeepSeek Harness jailbreak DSH plugin install fails: causes

A jailbreak DSH plugin that will not install is rarely one fault: it is usually one of three causes — an unreachable package or source, a profile and dependency problem, or a block by safety policy (source). The first two are ordinary install faults you can repair by the usual map; the third is the platform refusing on purpose. Below is a layered triage path and how to read the boundary. Whether such a plugin is worth installing at all is covered in DeepSeek Harness jailbreak explained.

Three causes behind a jailbreak DSH plugin that will not install

Split "it will not install" into source, dependency and policy first, because the three demand opposite responses: repair the first two, abandon the third (source). The typical shapes:

1. Unreachable package or source: a misspelled name, a deleted or private repo, a README install command that does not match the real package, an unpublished npm package, or a network or mirror that cannot reach it — the error points at "not found / cannot fetch".
2. Profile and dependency trouble: dependencies in the profile directory built by a different pnpm major, a plugin declaring an unpublished dependency, or an unauthorised build script — the install aborts or appears to succeed without taking effect.
3. Blocked by safety policy: the plugin is fetchable, but the platform refuses to install or activate it by rule. This is not a bug, and retrying, switching mirrors or editing the command changes nothing.

Identify the category before deciding whether to keep going: treating cause two as cause three wastes effort, and treating cause three as cause two is more likely to lead you into operations you should not run.

Reading the original error: a keyword map for a jailbreak DSH plugin

The error text names the layer, so the fastest triage is to map the keyword you see to one of the three causes before changing anything (source).

One rule of thumb: only the first four rows are worth acting on. The last row is a deliberate boundary, and treating it as a repairable fault is where people start running commands they should not.

DSH plugin triage step by step: from package and source to profile and allowBuilds

The order is read the original error first, then narrow layer by layer: whichever layer the message names is the only one you inspect — do not start by reinstalling.

1. Read the original error. After dsh plugin --profile web add github:<owner>/<repo>, see which category the keywords point to: 404 / not found suggests source, build / allowBuilds / dependencies suggests dependencies, not permitted / denied / policy suggests a block. The general failure map is in the plugin install failure map.
2. Verify the package name and source. Compare against the install command in the plugin README, confirm the repo is publicly reachable and the name is spelled and cased correctly; github: installs and npm package names are two separate sources, so do not mix them.
3. Check the profile and dependencies. Confirm the target is $DSH_HOME/profiles/web; if a pnpm major mismatch or an unpublished dependency is the cause, those have dedicated fixes in dsh plugin install stuck on dependencies.
4. Look at build authorisation. If the error is about the build being blocked, that is an allowBuilds authorisation matter rather than a bad package; the escalation ladder is in fix dsh plugin add allowBuilds.
5. Confirm whether it is a policy block. If none of the above matches and the wording reads not permitted or denied, jump to the next section and stop trying to force the install.

A safety block is expected behaviour: the compliant DSH plugin route

When a safety policy blocks a jailbreak plugin from installing or taking effect, that is expected behaviour rather than a fault — these boundaries are enforced by the framework, and neither model wording nor install tricks change them (source). Two things to accept:

1. A block is not a fixable bug. The platform refuses out-of-bounds capability by rule; retrying, switching sources or editing the profile cannot make it pass.
2. Installing it may still not help. Even if some path got it installed, a jailbreak plugin can only influence prompts or the interface — never tool gates and the sandbox. That is the usual reason a plugin installs and then does nothing.

So the right move when you are stuck on a policy block is to change how the need is met: use prompt-engineering plugins to adjust role, tone and output format, since they only change prompt text and never touch safety or permission boundaries. That category is filterable in the plugin market on DSH Plugin Hub, and installing them uses the standard dsh plugin --profile web add, which normally does not trip a policy block.

Confirming the install actually landed

"No error" is not the same as "recorded in the profile"; check the profile you meant to install into before debugging anything else.

# 1) Did the plugin land in the profile you think you installed into?
dsh plugin --profile web list
# the package should appear under the profile you actually run

# 2) Is it recorded in that profile's dependency manifest?
cat "$DSH_HOME/profiles/web/package.json"
# look for the package under "dependencies"

Expected: the package shows up both in the profile listing and in that profile's dependencies. If step 1 shows it under a different profile than the one you run, --profile was the mismatch — not the package. If it is absent from both but the command reported success, you most likely authorised a build for a package that was never added to this profile.

Notes on jailbreak DSH plugin installs and blocks

Classify "it will not install" first, then treat a block as expected behaviour, and most of the confusion resolves.

1. Classify before acting: source, dependency and policy demand opposite responses.
2. Read the original error: inspect the layer it names rather than reinstalling blindly.
3. Do not mix sources: github: and npm package names are separate sources that conflict when mixed.
4. Build authorisation is not a package problem: allowBuilds errors are authorisation matters, not an unusable repo.
5. Do not force a block: a policy block is a deliberate boundary with no reliable override.
6. Installed does not mean effective: a jailbreak plugin cannot change tool gates or the sandbox.
7. Stay compliant: prompt-engineering plugins keep risk bounded, and general install faults are mapped in the plugin install failure map.

Common misconceptions about jailbreak DSH plugin installs

Five beliefs that send people down the wrong path:

1. "If it will not install, the repo is just down." Not necessarily — a policy block is not a network fault, and re-checking mirrors will never clear it.
2. "A retry with a different mirror will get past a block." No — the block is a platform rule, not a fetching problem.
3. "allowBuilds means the package is broken." No — it is an authorisation gate, and the package was usually fetched fine.
4. "Once installed, it will bypass tool gates." No — a plugin can influence prompts and the interface, never the framework's gates or sandbox.
5. "Any install error can be brute-forced." No — the three causes demand opposite responses, and one of them explicitly has no fix.

Source: DeepSeek Harness CLI README, DeepSeek Harness docs - process sandbox.