ChatGPTClaudeGrok / X / CursorGemini

Installing dsh offline: mirrors, cache, tarballs

Install & Get StartedPublished 2026-11-02Author: DeepSeek Plugin Market
dsh installofflineintranetnpm mirrorintegrity
Three ways into an isolated network: a private registry, npm cache warm-up, and packed tarballs. Prepare, transfer, then verify hashes and versions.

The hard part of an intranet install is not the command; it is carrying the right packages and dependencies in, then proving they arrived intact. Pick one path by environment: a private registry, packed tarballs, or a warmed cache.

dsh offline install: three kinds of no network

The restriction level decides the path; choosing wrong wastes the trip.

EnvironmentViable pathPrerequisite
Reaches a private registryMirror syncPackage, plugins, and dependencies synced
Fully isolated, few machinesOffline tarballA transfer channel that is allowed
Fully isolated, many machinesCache warm-upSame architecture as the warm-up host

Confirm before acting. Run npm config get registry on the target; if it answers, you are on the mirror path, and only then consider moving packages.

dsh offline path one: private registry

The crux is not changing the registry setting; it is whether the version and its dependency tree exist inside it.

  1. On a connected machine, confirm the version: npm view @deepseek-ai/dsh versions;
  2. Have an administrator sync that version into the private registry;
  3. On the target, confirm the registry setting took effect;
  4. Re-run npm view @deepseek-ai/dsh@<version> on the target and require output;
  5. Only then install or run with npx.

A 404 almost always means an incomplete sync: a synced package with unsynced plugins and transitive dependencies, so dsh installs while plugins do not. Document which versions and plugins are mirrored so nobody rediscover it one failure at a time.

dsh offline path two: tarballs

For one or two isolated machines, tarballs are the most reliable path because they depend on neither cache state nor registry configuration.

Prepare on a connected machine:

  1. Run npm pack @deepseek-ai/dsh@<version> to produce a .tgz;
  2. Do the same for every plugin you need;
  3. Record versions into a manifest;
  4. Transfer the files and the manifest.

Install on the target:

  1. Confirm Node is ready: node -v;
  2. Install globally from the file: npm install -g ./deepseek-ai-dsh-<version>.tgz;
  3. Compare dsh --version with the manifest;
  4. Install plugins with dsh plugin --profile web add <path-to-tarball>;
  5. Restart and confirm the plugins appear in the list.

Tarballs still resolve dependencies. If a dependency exists neither locally nor in an internal registry, the install reaches out to the network — the most common offline failure. Pack the dependencies or provide a registry that covers them.

dsh offline path three: cache warm-up

Warm-up suits many machines with no registry, at the cost of coupling to architecture and cache layout.

  1. On a connected machine, run npm cache add @deepseek-ai/dsh@<version>;
  2. Confirm integrity with npm cache verify;
  3. Locate the cache with npm config get cache;
  4. Copy the cache directory to the same path on the target;
  5. On the target, run npx --offline -y @deepseek-ai/dsh@<version> web.

--offline makes a missing package fail immediately instead of hanging. During diagnosis, this output is more useful than npx's default retries.

Native modules are the blind spot. If the warm-up host and the target differ in architecture — arm64 to x64, for example — a cached package may still fail, and the target needs build tooling.

dsh offline verification and failure signals

A transfer without verification is not a transfer, because corruption and absence look the same: it will not install.

  1. SHA-256 of the package matches on both machines;
  2. dsh --version matches the manifest;
  3. The plugin count matches expectations;
  4. The first startup log has no module resolution errors;
  5. One message returns an answer.

Use the platform hash tool for step one. Compare both numbers; if they differ, copy again rather than "trying the install to see".

When verification fails, classify the failure before re-preparing anything.

SymptomLikely causeAction
404 during installVersion or dependency missing from the registrySync it, do not retry blindly
Network error during installTarball still has unmet dependenciesPack them or provide a registry
Installs, then reports missing modulesIncomplete package or wrong architectureRe-transfer and check architecture
--offline reports a missing packageThe cache lacks that versionRe-warm and verify the cache

"It will not install" is four different causes above. A signal, not a slogan, decides the fix.

dsh intranet practice and next steps

One-off delivery uses tarballs; ongoing use needs a registry.

  1. Maintain an internal list of installable dsh and plugin versions;
  2. Validate each upgrade on a test machine before syncing it inward;
  3. Record the dsh version and install path per machine;
  4. Never distribute a DSH_HOME with the package; configuration and credentials should be generated per machine.

DSH_HOME is not part of the installer. It defaults to ~/.dsh, and shipping the package transfers neither sessions nor credentials; data migration is a separate job.

Path chosen and transfer verified, only then start. For npx mirror details, read npx and offline mirrors. For slow downloads and registry settings, read slow downloads. For package integrity, read plugin package integrity. For a minimal setup, read minimal dsh install.

Sources: DeepSeek Harness docs, dsh CLI README, npm docs: npm pack

ChatGPTClaudeGrok / X / CursorGemini

FAQ

The target machine has no network at all. What must I prepare in advance?

Three things: a dsh package built for the target architecture, a Node runtime the target can use, and the plugin packages you intend to install. The dsh package does not include Node, so a machine without it cannot start even with the tarball.

Our private registry exists, yet installing dsh still returns 404. Why?

A 404 during a dsh install over a private registry usually means the version or its dependencies were never synced. Use npm view @deepseek-ai/dsh versions against the private registry to confirm the version exists, then verify that plugin packages and their transitive dependencies are mirrored too.

How do I confirm a transferred offline package was not corrupted?

Confirm an offline dsh package was not corrupted by computing SHA-256 on both machines and comparing before installing. After install, check dsh --version against the expected version. Both steps passing is the definition of a reliable transfer.

For an intranet, should I warm the cache or ship tarballs?

For dsh inside an intranet, many machines that reinstall often favor a private registry, while one or two machines delivered once favor tarballs. Cache warm-up is weakest across architectures because native modules may still need compilation on the target.

Related Terms

private registry
A private registry is an npm source hosted inside a company network; pointing the client at it makes resolution and installs come from internal storage.— npm docs
cache warm-up
Cache warm-up is the practice of downloading packages into the npm cache on a connected machine so the cache can be copied to a target that has no network.— npm docs
offline package
An offline package is a `.tgz` produced by `npm pack`, installable by local path without contacting any registry.— npm docs: npm pack
DSH_HOME
DSH_HOME is the data root for DeepSeek Harness, defaulting to ~/.dsh, holding settings, sessions, plugins, and credentials; no installer carries it.— DeepSeek Harness docs

Sources