Open the local Web UI
Visit http://127.0.0.1:3080 after the command starts successfully.
Install DeepSeek Harness (DSH)
Run the official DSH package without a global install, open its local Web UI, and verify the preview version before adding community plugins or Skills.
Quick answer
npx @deepseek-ai/dsh webThen open http://127.0.0.1:3080. DeepSeek Harness is still a developer preview.0.1.0-rc.6Current npm version at snapshot
@deepseek-ai/dshOfficial npm package
127.0.0.1:3080Documented local Web UI
PreviewBreaking changes are possible
Step 1
Launch the Web UI with npx
The official README documents one direct command. npx resolves and runs the package without requiring a permanent global installation.
npx @deepseek-ai/dsh webterminalBefore running it: verify that the package name is exactly
@deepseek-ai/dsh, review the official repository, and avoid copying commands from an unattributed mirror.Step 2
Open and verify the local service
Record the resolved version
The current source snapshot reports 0.1.0-rc.6. Pin and retest when moving beyond exploration.
Keep it local first
Do not expose a preview service publicly or connect sensitive credentials before reviewing authentication, network and plugin behavior.
Next: plugins
Plugins extend Harness runtime surfaces. SkillVetAI discovers community repositories through the GitHub dsh-plugin topic, but does not treat discovery as a security or compatibility certification.
Next: Skills
Skills are optional instruction assets with their own discovery roots, names and invocation controls. They are not equivalent to plugins.
Read the Skill format guide →Troubleshooting
Common preview-stage checks
The command resolves the wrong package or fails
Confirm the scoped package name, Node/npm availability and network access. Compare the package link from the official repository rather than searching for an unscoped lookalike.
The Web UI does not open on port 3080
Read the terminal output first. The process may have failed, exited, or found the port occupied. Do not assume the service started merely because npm downloaded a package.
Should I install community plugins immediately?
No. Establish a clean baseline first, then inspect each plugin's source, dependencies, permissions and maintenance history before adding it.
Is this a stable production release?
No. DeepSeek labels Harness a developer preview, and the current npm version is a release candidate. Compatibility-breaking changes should be expected.
Primary sources