Updated 2026-11-13 · Cameron Voss and West Mao

DeepSeek Harness Sidebar Too Limited? Inside dsh-soup, a Five-Part Replacement (Nov 2026)

The built-in sidebar is fine until you run long sessions, watch token throughput, or need to read a file without opening another app. dsh-soup rewrites that panel with five additions borrowed from JupyterLab and pi-web.

Why does the default sidebar feel limited?

A coding harness sidebar has to do four jobs at once: show where you are in the session, show what the run is costing, show the files, and let you read them. The official panel does the first two in a single line each, and it keeps file preview inside a narrow dock.

That layout is compact, which is why it ships by default. The problems appear under load. A Goal with several acceptance conditions wraps into an ellipsis. A long source file turns the preview into a horizontal scrollbar. Reading a PDF means leaving the harness entirely.

dsh-soup keeps the same placement and changes the contents. The author's design brief was explicitly anti-feature: everything added maps to a daily action, and nothing is there to look clever.

What does dsh-soup actually add?

Five things. Each one is small on its own; together they remove most of the alt-tab traffic.

The five additions and when each one earns its place
SurfaceWhat changesWhen it earns its place
Token throughput badgeLive tokens per second in the header, no second clickLong generations, when you want to know if the run slowed down or stalled
Goal status barMulti-line instead of one truncated lineGoals with several constraints, where the last condition is the one that matters
File treeUpload, folder collapse, right-click menuJumping between files without opening a separate editor
Preview paneCentered and wide, PDF, HTML, Markdown, codeReading a long file, where the docked panel forces sideways scrolling
Edit in previewClick the content, edit, save, return to previewFixing one line without a full editor round trip

The badge is a derivative, not a total

The headline feature is the throughput badge, and it is the one most likely to be misread. Tokens per second tells you how fast the current stream is moving. It says nothing about how many tokens the session has spent, or what the remaining budget is.

Read it like a speedometer, which is the comparison the author makes. A speedometer does not tell you how much fuel is in the tank. If the rate drops to zero mid-run, that is the signal worth acting on: a stalled stream, a rate limit, or a tool call waiting on something.

The design follows pi-web, so the visual language should be familiar if you have used that interface. The badge sits in the app chrome rather than inside a session pane, which is why it never needs a menu.

Why a multi-line Goal bar matters more than it sounds

Harness Goals are not single sentences. A typical one carries the task, the acceptance conditions, and the constraints on how to get there. When the sidebar shows one line, the visible part is the task and the hidden part is the acceptance criteria.

That is exactly backwards for review. You end up opening the goal definition to check whether the agent actually met the bar. A multi-line status bar keeps the conditions on screen while the run proceeds, so you can catch a wrong interpretation early instead of at the end.

What does JupyterLab-style mean in practice?

The file tree copies a specific interaction model rather than a visual style. Directories collapse. Upload is available from the panel. Right-clicking a file offers three actions: open with the system default program, download, and delete.

The right-click menu is the part that saves time, because those three actions are the ones that otherwise require a terminal. They are also the ones with consequences. Delete in this menu is a real delete, not a move to a trash folder. If the harness workspace is the only copy of a draft, treat that item as permanent.

The centered preview changes how you read code

Docked previews allocate width to the sidebar, and code does not wrap well. A 120-character line in a 380-pixel panel becomes a horizontal scrollbar exercise. Moving the preview into the main column gives it the full width of the window, which is the difference between skimming a function and reading it.

Editing inside the preview is the second half of that idea. Click into the rendered or highlighted content, make the change, save, and the pane returns to preview. For a one-line fix during a review pass, that loop is faster than opening an editor, finding the file, and saving.

One caveat that does not appear in the feature list: HTML preview executes page code. Only preview HTML you trust, for the same reason you would not open a random local page in a browser with your session cookies.

How do I install dsh-soup?

There are two routes, and they suit different habits. The first is to open dsh-market inside DeepSeek Harness, search for dsh-soup, and install from there. This is the route to prefer, because the market entry tracks the plugin manifest.

The second is to hand the project source to an agent and let it install. The author documents this route for people who already have an agent session open and would rather not switch panes.

After installation, reload the harness window. The badge appears in the header, and the sidebar picks up the new tree. If neither shows up, the plugin did not register, and reinstalling from the market is faster than debugging a half-loaded panel.

dsh-market  ->  search: dsh-soup  ->  Install  ->  reload the harness window

How do I verify the install?

Run these five checks once after install. They cover every surface the plugin touches.

Post-install verification
CheckWhat confirms it worked
Throughput badgeIt moves during a generation and stops when the stream ends
Goal barA multi-line Goal wraps instead of truncating
File treeTwo nested folders collapse and expand
Context menuOpen-with-system and download work; test delete on a scratch file only
Preview editingClick, change one character, save, and the pane returns to rendered mode

Where are the trade-offs?

It is a community plugin, so the maintenance model is one person plus contributors. That is normal for this ecosystem and worth knowing before you make it part of a daily workflow. Pin the version you installed, and check whether the manifest still loads after a harness upgrade.

The file operations run with the harness's own permissions. A sidebar that can delete files is convenient and also a footgun; if you keep generated artifacts in the workspace, back up anything you cannot regenerate.

The throughput badge costs a small amount of render work per update. On a laptop that is invisible. On a low-power machine running a long generation, it is one more timer in the UI thread, so if the panel feels heavy, the badge is the first thing to disable.

Should you replace the official sidebar?

If you run short sessions and rarely open files, the default panel is enough, and a plugin is extra surface area for no gain. If your sessions are long, your Goals are conditional, or you read source files while the agent works, the five additions map to five real interruptions that disappear.

The honest summary is that dsh-soup is a better panel, not a better harness. It will not change how the agent plans or how many tokens a task costs. It changes how often you leave the window to answer a question the window could have answered itself.

FAQ

Does dsh-soup work outside the desktop app?

The plugin targets the DeepSeek Harness desktop surface, where the sidebar and system default program actions exist. The right-click open action depends on the host OS, so expect the most polish on the platform the author uses.

Does the throughput badge report cost?

No. It reports tokens per second for the current stream. For spend, use your Coding Plan usage view, which reads the stored quota rather than a UI estimate.

Can I recover a file I deleted from the sidebar menu?

Only if another copy exists. The menu deletes the file; it does not move it to a trash directory. Use version control for anything you would miss.

Will it fight with other sidebar plugins?

Two plugins that both replace the sidebar will conflict. Install one at a time and reload between changes, so you can tell which panel is rendering.

dsh-soup is worth installing if the sidebar is where your session slows down, not because it looks better. The badge tells you when a stream stalls, the Goal bar keeps acceptance conditions visible, and the centered preview removes the most common reason to leave the window. Just treat delete as permanent and HTML preview as code execution.