Start with a disposable or non-sensitive workspace when evaluating this DeepSeek Harness plugin. Confirm that the Web profile starts normally, then install the pinned release, reload only as directed by the upstream README, and inspect which files, terminal sessions, and previews become available. This staged approach keeps a workspace sidebar experiment separate from a production repository until you understand its permissions and behavior.
DSH Better Sidebar
DSH Better Sidebar is a VS Code-style workspace sidebar for DeepSeek Harness Web with session-scoped files, editing, terminal, Git, previews, and extension tabs.
Review snapshot
- Manifest
- Passed
- Install
- Not tested
- Runtime
- Not tested
Static compatibility snapshot dated 2026-08-14; install and runtime remain independent checks.
Install / upstream documentation
Install the pinned release deliberately
This bundle uses an upstream-documented installation path pinned to the reviewed release. Read the linked README and inspect the source before you install it.
Upstream command · profile web
npx -y --package @deepseek-ai/dsh dsh plugin --profile web add dsh-better-sidebar@0.10.3This version-pinned DSH CLI command is documented by the upstream repository. AgentPlugin.net has not executed it, and showing it is not a safety, compatibility, or runtime guarantee.
Source: Pinned upstream README at efb2e2bPlugin brief
What DSH Better Sidebar adds to DeepSeek Harness
DSH Better Sidebar is a DeepSeek Harness plugin for people who want the DeepSeek Harness Web profile to feel closer to a focused development workspace. Instead of treating a chat session as an isolated transcript, it places files, editors, terminal output, Git context, previews, and extension tabs around the active session. The result is a workspace sidebar that makes it easier to keep code, notes, and agent activity in view without constantly switching browser tabs.
The plugin is most useful when a DeepSeek Harness session touches more than one artifact. A coding task may involve reading a repository, editing several files, checking a diff, running a command, and opening a preview. DSH Better Sidebar groups those surfaces into a predictable layout. It is not a replacement for a full IDE, and it should not be described as one; it is a workspace sidebar designed for the Web profile and the workflow that happens around an agent session.
This listing records the release as a DSH Bundle because the pinned package and patch evidence describe that distribution path. That label explains the source snapshot shown here; it does not certify the software, promise a successful install, or make the plugin appropriate for every project. DeepSeek Harness is still in developer preview, so a compatible-looking release can change behavior when the host runtime, dependencies, or profile configuration changes.
Evaluation workflow
Evaluate DSH Better Sidebar with clear boundaries
Use the file and Git panels as context aids, not as evidence that changes are safe. Review generated diffs, inspect commands before running them, and keep normal version-control practices in place. The terminal and filesystem features can expose project material to a workflow that is more capable than a simple read-only browser view, which is why the execution-risk record remains visible on this page.
If the layout looks duplicated or unstable after an update, compare the active profile with the pinned upstream instructions before adding more configuration. The source notes warn against leaving an older manual registry or patch mount active beside the Bundle path. Follow the pinned README before changing configuration, and do not add an extra mount to work around a duplicated sidebar.
Verification ledger
Evidence, not installation claims
Manifest
PassedThe npm release gitHead matches the pinned source commit; package.json declares dsh.bundle.patch → ./cordis.patch.yml, and the patch is a YAML array inserting the dsh-better-sidebar row.
Checked Aug 14, 2026
Install
Not testedThe npm release and upstream README were confirmed, but AgentPlugin.net has not run the installation.
Runtime
Not testedNo clean-profile DSH Web smoke test has been completed by AgentPlugin.net.
| Layer | Result | What was checked |
|---|---|---|
| Manifest | Passed | The npm release gitHead matches the pinned source commit; package.json declares dsh.bundle.patch → ./cordis.patch.yml, and the patch is a YAML array inserting the dsh-better-sidebar row.[Aug 14, 2026] |
| Install | Not tested | The npm release and upstream README were confirmed, but AgentPlugin.net has not run the installation. |
| Runtime | Not tested | No clean-profile DSH Web smoke test has been completed by AgentPlugin.net. |
Source or manifest review can be recorded while Install and Runtime remain not-tested. Treat these as separate verification layers.
Execution surface
Prepare, build, and code-execution review
prepare
review recorded
The package declares prepare: tsdown. Source or Git installs can execute this build step; prefer the pinned npm release unless you have reviewed the source.
build
review recorded
The documented installer may request build approval for native dependencies such as node-pty. Treat approval as permission to run dependency build code.
code execution
review recorded
The plugin exposes terminal, filesystem, Git, preview, and WebSocket features inside the active workspace. Review its trust boundaries before use on sensitive projects.
configuration
notice recorded
Do not keep an older manual registry or patch mount enabled alongside this Bundle; the upstream README warns that both paths can mount the sidebar twice.
Declared scope
Capabilities and prerequisites
Capabilities
- Session-scoped file explorer and editor
- Integrated terminal and Git workspace
- Document, media, and browser previews
- Extension tabs for third-party DSH plugins
- Sub-agent workspace integration
Prerequisites
- A working DeepSeek Harness Web profile
- Node.js 20 or newer
- pnpm 10 or newer
- Review any native build-script approval before allowing it
Frequently asked questions
DSH Better Sidebar FAQ
What is DSH Better Sidebar?
DSH Better Sidebar is a DeepSeek Harness plugin that adds a VS Code-style workspace sidebar to the DeepSeek Harness Web profile. Its declared scope includes session-scoped files and editing, terminal and Git views, previews, extension tabs, and sub-agent workspace context.
What is the primary use case for this workspace sidebar?
It is intended for agent-assisted coding and project work where a single session needs files, commands, diffs, previews, and extension surfaces nearby. It helps organize those surfaces; it does not replace source control, code review, or a full desktop IDE.
How do I install this DeepSeek Harness plugin?
Use the version-pinned command shown in the installation section, then follow the linked upstream README for any reload or profile steps. The command comes from the upstream DeepSeek Harness plugin mechanism, but AgentPlugin.net has not run it and cannot guarantee that it will work in your environment.
Why is the release version pinned to 0.10.3?
A pinned version makes the command, npm package, source commit, and review snapshot refer to the same known release. It reduces ambiguity during evaluation, but it does not freeze DeepSeek Harness itself or prevent compatibility changes in a developer-preview ecosystem.
Has AgentPlugin.net tested the install or runtime?
No. This page records static manifest evidence, while installation and runtime are explicitly marked not tested. Read the repository and README, evaluate it in a controlled profile, and make your own compatibility decision before using the plugin on important work.
Why are prepare and build warnings shown?
The package declares a prepare build step, and upstream installation may request approval for native dependency builds such as node-pty. Approval can execute dependency build code, so review the source and understand the workstation and repository access involved before proceeding.
Can I keep an older manual mount enabled?
The upstream notes warn that combining an older manual registry or patch mount with this Bundle can mount the workspace sidebar twice. Check existing profile configuration first and avoid layering both approaches unless the upstream project specifically documents that setup.