Skip to content

alooshxl/dsh-session-pins

30Last commit Aug 13, 2026

dsh-session-pins DSH plugin

Session Pins lets you pin, unpin, and open sessions from a dedicated menu in the sidebar footer. Pins are stored in browser localStorage and survive page reloads. The plugin works in both wide and rail sidebar modes, showing pin count and an empty state when no sessions are pinned.

How to install the dsh-session-pins DSH plugin

dsh plugin --profile web add github:alooshxl/dsh-session-pins#v0.1.0

Copying does not run this command. Review the repository and version before installing the dsh-session-pins DSH plugin.

dsh-session-pins DSH plugin data source

dsh-session-pins DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-session-pins DSH plugin can do

  • Pin the current session (non-blank, non-subagent) from the sidebar footer action.
  • Unpin a session directly from the menu or use the 'Unpin current session' option.
  • Open a pinned session in the current workspace, provided it is not archived, subagent, or stale.
  • Display a persistent pin count in the sidebar footer action.
  • Support both wide sidebar (with label) and rail sidebar (icon-only with tooltip).
  • Store up to 100 pins in localStorage under the key `dsh.session-pins.v1`.

Where the dsh-session-pins DSH plugin fits

  • Keep your most important sessions easily accessible without scrolling through the session list.
  • Quickly switch between a few frequently used sessions during a research or coding session.
  • Maintain a curated set of reference sessions that you revisit often.
  • Recover a pinned session that was accidentally closed by reopening it from the menu.

Who the dsh-session-pins DSH plugin is for

  • DeepSeek Harness users who manage multiple sessions and want rapid access to key ones.
  • Developers and researchers using DeepSeek Harness in the web profile who need session organization.

dsh-session-pins DSH plugin limitations

  • Pins are browser-local only; they do not sync across devices, profiles, or different origins.
  • Requires DeepSeek Harness 0.1.0-rc.6; compatibility may break with newer release candidates.
  • Cannot pin a blank or subagent current session; previously stored subagent pins remain removable but cannot be opened.
  • Archived sessions cannot be opened due to Harness version limitations; the plugin omits the Open button and explains the restriction.
  • If localStorage is blocked or throws, pins are kept in memory for the current page but lost on reload.

dsh-session-pins DSH plugin: from the repository README

Quoted from the alooshxl/dsh-session-pins README, the upstream source of the dsh-session-pins DSH plugin. Copyright remains with the original authors.

`@dsh-external/dsh-session-pins` adds a persistent pinned-session menu to the DeepSeek Harness web sidebar. The plugin answers [DeepSeek Harness Discussion #63](https://github.com/deepseek-ai/deepseek-harness/discussions/63), which asks to keep valuable sessions easy to reach. Harness does not expose a public session-row action slot, and replacing the stock session browser would couple a plugin to private UI source. Session Pins therefore contributes one root-scoped action through the public `sidebar.footer.action` slot. It does not patch or replace the host. ## Compatibility status The source, automated contracts, and package artifacts target `@deepseek-ai/dsh@0.1.0-rc.6`. DeepSeek Harness is in developer preview, so a new release candidate may break this plugin until compatibility is reviewed. The automated suite includes an isolated, keyless rc.6 profile smoke: it installs this repository through the published CLI, composes the plugin row, boots on an ephemeral loopback port, reads the root boot manifest, and fetches the package-name browser module route. Task 7's manual wide/rail visual acceptance remains pending and is not claimed here. ## User experience - **Wide sideba

Read the full READMERepository license: MIT

dsh-session-pins DSH plugin questions

How do I pin a session?

Make sure your current session is not blank and not a subagent session. Then click the pin icon (with the label 'Pinned sessions') in the sidebar footer. The current session will be added to the top of the pin list. You can also open the menu and click 'Pin current session' if it appears.

Why can't I open a pinned session that is archived?

DeepSeek Harness 0.1.0-rc.6 immediately clears an archived session ID when you try to open it via `sessions.open()`, and there is no public unarchive operation. Session Pins deliberately omits the Open button for archived pins and shows a message explaining the limitation. You can still unpin or go back.

Do my pins sync across devices?

No. Pins are stored in browser localStorage only, keyed under `dsh.session-pins.v1`. They do not sync across devices, browser profiles, or different origins. Each browser and profile has its own independent pin list. If you need the same pinned sessions on another device, you must pin them again there.

How do I upgrade the plugin to a new version?

Use the `dsh plugin --profile web add` command again with the new Git tag, for example `dsh plugin --profile web add github:alooshxl/dsh-session-pins#v0.1.1`. Do not use the `update` command for Git refs. If you want an immutable installation, replace the tag with the full commit SHA.

What happens if I open a pinned session that was deleted?

If the session no longer exists (stale id), the pin will show as 'Unavailable: id' and the Open button will be hidden. You can still unpin it or go back. If an open fails for any other reason, the menu remains usable, an error message is shown, and the unpin option stays available.