What counts as a workbench plugin, and is it the same as an editor plugin?

Workbench plugins and editor plugins are not the same. Workbench covers sidebar, editor, and terminal, while editor plugins are one area.

Should I install a sidebar, editor, and terminal plugin at once?

Installing a sidebar, editor, and terminal plugin at once is not advisable in DeepSeek Harness. Add one, verify it, then add the next.

The editor plugin conflicts with built-in shortcuts. How do I resolve it?

An editor plugin that conflicts with built-in shortcuts needs its shortcut settings checked and the conflict resolved. Alternatively, disable the built-in shortcut.

Will workbench plugins slow down DeepSeek Harness?

Whether workbench plugins slow DeepSeek Harness down depends on what they inject. Sidebar and editor plugins that hook rendering add startup and drawing cost.

Editor and workbench plugins: sidebar, editor, terminal

Workbench plugins extend three areas: sidebar, editor, and terminal. They are not one category; installing several at once usually creates conflicts and performance costs.

Three areas

Choose by which area you want to improve.

Area	Improves	Typical plugin	Risk
Sidebar	Navigation and layout	Sidebar enhancement	Layout conflicts
Editor	Viewing and editing	Editor enhancement	Shortcut and rendering conflicts
Terminal	Commands in the interface	Terminal panel	Path and permission issues

Sidebar changes space and entry points. Sidebar plugins rearrange sessions, files, and plugin entries, affecting navigation rather than editing (source).

Editor changes viewing and editing. Editor plugins add highlighting, previews, and shortcuts; two plugins in one area are likely to conflict.

Terminal brings commands in. Terminal plugins embed a shell, convenient for paths and scripts but with permission boundaries.

Sidebar and layout

The most visible change and the most likely to conflict.

Confirm the sidebar structure you want: wider, multi-column, or grouped.
Install one sidebar plugin and restart.
Check session list, files, and plugin entries.
Check narrow screens and small windows.
Add a second only when the first is stable.

Layout conflicts show as overlapping or disappearing entries, and a wider sidebar squeezes main content. Install one at a time; comparing two at once makes the cause unclear. Verify long prompts and code after changing width.

Editor and shortcuts

Editor plugins change editing; shortcuts are the main conflict.

Confirm what is added: highlighting, preview, formatting, or shortcuts.
Check shortcut conflicts with the built-in and other plugins.
Test on different file types.
Confirm large files do not lag.
Record the configuration.

Shortcut conflicts are common and easily mistaken for bugs, while large files add a hidden rendering cost. A key does nothing or the wrong action occurs; check key mappings and plugin priorities. Highlighting and preview on very long files can stall the interface.

Terminal and execution

The terminal plugin embeds a shell, convenient with boundaries.

Confirm which shell and working directory.
Check environment variables and PATH.
Confirm sandbox and permission limits.
Run a harmless command first.
Confirm the exit code and output.

The terminal is not the host shell. Sandbox and execution policies may differ; running a command successfully in a system terminal does not mean it works in the plugin.

Path differences are common. Working directory and environment variables differ from the terminal started by the CLI.

Install order and conflicts

One area at a time; verify before adding.

Install the sidebar plugin and verify.
Install the editor plugin and verify.
Install the terminal plugin and verify.
If two plugins touch the same area, keep one.
Record the working combination.

Same-area plugins conflict most. Sidebar plus sidebar, editor plus editor; different areas may share style or shortcuts.

Version matters. Upgrading one plugin may break another; upgrade separately.

Performance and trade-offs

Workbench plugins trade features for resources.

Startup: hooks and injection add loading time.
Rendering: complex layouts and highlighting add drawing cost.
Memory: embedded terminals and previews occupy memory.
Measure: compare startup and panel response before and after.

More is not better. A sidebar and editor plugin cover most needs; stacking terminal and preview adds cost without benefit.

Disable unused features. Plugins with switches should turn off unused ones.

Choice

Choose by task and verify.

Need	Area	Note
Too many sessions, hard to find	Sidebar	Grouping and width
Frequent code reading	Editor	Highlighting and preview
Run commands without switching	Terminal	Permissions and paths
Full development	Two or three	Install in order

Start with the most frequently used area. A sidebar plugin often delivers the most obvious benefit; the editor and terminal come later.

Do not install "for completeness." Each adds maintenance and conflict risk.

Next steps

Area, order, verification. For sidebar plugins specifically, read The dsh-better-sidebar plugin. For image and vision plugins, read Image generation and vision plugins. For plugin categories, read What DSH plugin categories exist.

Sources: dsh-better-sidebar plugin page, DeepSeek Harness docs, dsh CLI README