AI Agent Hub
Back to plugins
🖥️

dsh-plugin-cli-session

Client Updated 2026.08.18

Run the following command in DeepSeek Harness:

dsh plugin install ghbhiee/dsh-plugin-cli-session

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

Install it in the DeepSeek Harness CLI by running dsh plugin install ghbhiee/dsh-plugin-cli-session; the full source is at https://github.com/ghbhiee/dsh-plugin-cli-session and ships with a pre-built lib/ directory, so no build step is required.

About this plugin

The headless runner shipped with DeepSeek Harness is one-shot: it answers once and is discarded, with no way to continue the previous conversation. In practice, many teams end up maintaining two hand-copied profile runners (a conversational one and a claude -p-style one) whose core logic drifts into near-duplicates over time. dsh-plugin-cli-session merges them into a single plugin: one shared implementation for session resolution, the drive loop, summarisation, and exit handling, with the only differences expressed as configuration.

It gives the CLI real session lifecycle management: --resume, --list, and --session scope history by profile directory and sessionTag so two profiles in the same folder never see each other; -o json and -o stream-json emit structured envelopes (type, result, session_id, usage, etc.) on a clean stdout for pipe-friendly parsing; --workdir creates and enters a directory before the session starts. At boot the plugin validates its configuration (blank sessionTag, negative exitGraceMs, missing request) and refuses to silently create an empty session that would waste a model call.

It is built for developers who drive DeepSeek from the terminal in scripted workflows, engineers who need structured JSON responses inside CI or automation pipelines, and teams that currently maintain two profile runners and want to consolidate duplicated code under unified session management.

Use Cases

  • Resuming a prior DeepSeek conversation from a script without re-pasting context
  • Consuming a structured JSON envelope via -o json inside a CI pipeline
  • Consolidating two diverged profile runners into one plugin to eliminate duplicate maintenance

Best For

  • Developers who drive DeepSeek from terminal scripts
  • Engineers who need to parse JSON responses in automation pipelines
  • Teams maintaining multiple profile runners who want unified session management