Better Sidebar
omdsh-dev
A sidebar platform for DSH — file, terminal, diff and agent pages, plus a service other plugins use to register their own tabs and file viewers.
L3
3.6k TypeScript
session
Sessions & Messages DSH plugins
Composer upgrades, session history, archiving and message workflow.
This directory lists 4 DeepSeek Harness plugins for Sessions & Messages. Their verification levels run L1 0, L2 2, L3 2, L4 0, L5 0: no listing here has been installed or run in a sandbox, so none claims L4 or L5. 0 have passed an automated security scan, and the other 4 are marked unverified rather than safe. Declared compatibility targets are unstated 2, ^0.1.5-rc.1 1, >=0.1.5-rc.1 1. Together these 4 listings carry 4,847 GitHub stars, led by Better Sidebar at 3,650. Licences are mainly MIT 3, Apache-2.0 1, and the code is written mostly in TypeScript, JavaScript. Every entry records its source repository, licence, declared harness target and a copy-ready install command; the most recently checked is Better Sidebar (2026-09-18). A verification level measures how far the install path was exercised — it is not a safety guarantee, so read the source before you install.
Session plugins work on the conversation itself: the composer where you type, the history you scroll, the sessions you archive, the way messages are attached and referenced. They rarely change what the model can do, but they change how much friction sits between you and it.
Look for plugins that respect session state rather than shadowing it, and prefer ones that store their data inside the profile directory so a reinstall does not erase your history.
How to choose in this category
Friction is the metric. Does the plugin make attaching a workspace path, reviewing an old session, or archiving a finished run faster without hiding state? Composer upgrades should keep references explicit — @file style mentions that point at paths are safer than silent whole-file inlining.
Persistence path is the second question. Local profile storage survives reinstalls you control. Cloud history is a different product decision; read the privacy story before you enable it.
What is mature versus thin here
Mature session plugins document where state lives, how history is searched, and what happens across upgrades. Thin ones restyle the input box and call it a workflow. Session-aware notification and IM bridges sit next door; they belong here only when the session binding is the point.
Common mistakes
Shadowing session state in a parallel store that drifts. Installing a history plugin that exports transcripts to a third party by default. Assuming a prettier composer includes safer file references — often it is the opposite.
What this category should not do
Session tooling should not become a second agent. If a composer upgrade also runs silent background tasks, it has crossed into orchestration and needs the same budget and approval controls. Prefer plugins that stay on the surface: typing, history, archive, reference.
Search and export features deserve a second look. A history index that keeps everything local is maintenance; one that uploads transcripts is a product decision you should make on purpose, not inherit from a default.
4 plugins
Editor's pick
At File
FSMargoo
Codex-style @file mentions that search workspace paths in the composer and attach a path reference — not file contents — to your prompt.
L2
513 JavaScript
DSH Synapse
liangmianya
A canvas session map for DeepSeek Harness — sessions, follow-ups and native forks as a browsable, draggable workspace, with DSH session logs remaining the only source of truth.
L2
404 JavaScript
dsh-tianshu-tui
huiliyi37
A full terminal workspace for DSH: streaming markdown and tool cards, 16+ themes, slash commands, session tabs and LSP diagnostics — a pure view layer that registers no prompt or tool surface.
L3
280 TypeScript