AI Agent Hub
Back to plugins
🖥️

dsh-session-id

Client Updated 2026.08.17

Run the following command in DeepSeek Harness:

dsh plugin install realpkuasule/dsh-session-id

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install realpkuasule/dsh-session-id in the DeepSeek Harness terminal to install this plugin; the source is at https://github.com/realpkuasule/dsh-session-id .

About this plugin

The session ID in DeepSeek Harness is the key identifier for debugging, archiving, and cross-session collaboration, yet the GUI never surfaces it by default. You end up reaching for DevTools or digging through the archive panel every single time. dsh-session-id closes that last mile: a small 11 px label sits permanently in the dock right below the composer, so you always know which session you are working in at a glance.

Interaction is deliberately minimal. Click the label to copy the ID; the plugin prefers navigator.clipboard and falls back to execCommand for older browsers. A brief green highlight and a "Copied" tick confirm the action, resetting after 1.6 seconds. Hover brightens the text, and the label is also selectable by mouse for quick re-reading. When no session is active the element simply does not render, leaving no empty space in the dock. Under the hood it is a pure UI plugin: it touches no host state, registers no HTTP endpoints, and follows the official slots.inject injection point and standard bundle distribution format. Zero permissions, zero side effects.

If you regularly need to grab and share DSH session IDs—pasting them into bug reports, handoff notes to a teammate, or just telling yourself which tab is which across a dozen open sessions—this plugin removes the DevTools detour for good. It installs as a single bundle, requires no build step, and needs no extra configuration.

Use Cases

  • Referencing the current session ID while debugging
  • Identifying and sharing session IDs during cross-session collaboration
  • Tagging session IDs when archiving conversation records

Best For

  • Developers who frequently need to retrieve and share DSH session IDs
  • Users debugging multi-session issues who need quick ID lookup
  • Engineers using DeepSeek Harness for team collaboration