Skip to content
DSH Themes

Switch language

Open navigation
Back to Learn
07Installation8 min readBeginner

GUIDE 07 · INSTALLATION

Install a Verified Release

Installation is a local profile mutation. Treat the catalog as evidence, the downloaded tgz as the object being authorized, and the previous exact state as your return path.

Last verified
Sep 6, 2026
Guide source baseline
0.1.3-alpha.1
Installation status
Check the selected item’s record
Verified scope
  • Fixed 0.1.3-alpha.1 source and item-level verification
  • Whole-artifact SHA-256 verification
  • Single direct web-profile theme
On this page
  1. Complete the preflight first
  2. Use exact local inputs
  3. Install one selected item

Complete the preflight first

  1. 01

    Read the runtime version

    This guide targets DeepSeek Harness 0.1.3-alpha.1 at source commit d347e703908d0406b7a7ef80e3a0e594d86b2215. The Alpha installation uses a build from that exact source revision. Check the selected item’s current package, profile, and test results separately; older receipts and screenshots do not establish compatibility with this Alpha.

  2. 02

    Inspect the current web profile

    Record the existing direct @dsh-themes/* dependency and exact version. More than one direct package is a conflict to resolve before installing.

  3. 03

    Use the controlled release download

    Prepare the exact published tgz in a restricted local artifact directory. Do not authorize a similarly named file from another source.

  4. 04

    Verify the complete artifact SHA-256

    Match the downloaded bytes to the catalog artifact digest and integrity. A payload digest inside the manifest is a different scope.

  5. 05

    Prepare the previous exact artifact

    If a theme is already active, keep its verified package and identity available before removing it.

Use exact local inputs

bash
RUNNER=/absolute/path/to/dsh-theme-manager/scripts/run-dsh.mjs
node "$RUNNER" --source --version
node "$RUNNER" --source plugin --profile web list --json
node "$RUNNER" --source plugin --profile web add /absolute/path/to/verified-theme.tgz --save-exact
node "$RUNNER" --source --profile web --dump-config
Command shape only. Replace the path with the already verified absolute artifact path.
  1. Confirm the direct dependency uses the expected package name and exact version, never a range.
  2. Confirm only one direct package under the @dsh-themes/* scope is active in the web profile.
  3. Restart DSH after adding, removing, or switching the package.
  4. Open the real web UI and verify the expected theme or skin identity before discarding any rollback material.

Installation references

Browse verified releasesSelect a published version with controlled evidence.Switch and roll backPreserve and consume an exact rollback record.

Install one selected item

Open the detail page, copy its task, and let the Agent check the current Harness version and target profile. After installation, open Harness and try the specific feature, not just the startup screen.

text
Install catalog item #NNNN using its current DSH Themes Skill and exact source. Check the Harness version, save the previous state, perform the installation, and verify the feature after restarting. Explain any setup I must complete.
A prompt to try

Common questions

Before you make a change

Answers about formats, compatibility, evidence, and rollback.

What does this guide verify?

This guide covers: Fixed 0.1.3-alpha.1 source and item-level verification; Whole-artifact SHA-256 verification; Single direct web-profile theme

What should I do first?

Installation is a local profile mutation. Treat the catalog as evidence, the downloaded tgz as the object being authorized, and the previous exact state as your return path.

Which boundary matters most?

This guide targets DeepSeek Harness 0.1.3-alpha.1 at source commit d347e703908d0406b7a7ef80e3a0e594d86b2215. The Alpha installation uses a build from that exact source revision. Check the selected item’s current package, profile, and test results separately; older receipts and screenshots do not establish compatibility with this Alpha.

Does installation configure paid services automatically?

No. An installed Plugin can still need your account, API key, subscription, or local service. The Agent should explain what is missing and let you configure it.

Continue learning

Previous guideChoose a Theme or a Full SkinNext guideCompare Light and Dark Modes

Continue from the verified evidence

Compare published artifacts or return to the installation documentation.

ExploreDocs