Who it is forA developer working through a problem in steps who wants DeepSeek to keep the earlier context.
The problemEach fresh one-shot run starts with no memory of the previous one, so every follow-up repeats the setup.
The outcomeA session id that lets follow-up prompts continue the same DeepSeek conversation while the broker is running.
What you need first
- Claude Code with plugin support
- Node >= 20 and a DEEPSEEK_API_KEY
- For /dsh:setup: Node >= 22.19, npm, and pnpm (enable with corepack)
- A git repo with local changes to review (for /dsh:review)
Steps
- Run
/plugin marketplace add cpj-dev/dsh-plugin-ccin Claude Code. - Run
/plugin install dsh@deepseek-dsh, then/dsh:setup. - Run
/dsh:run --session <task>to start a session. (inferred, check the README) - Run
/dsh:run --resume <follow-up>to continue it, then/dsh:runsto see the session. (inferred, check the README)
Prompt for your agent
Using the cpj-dev/dsh-plugin-cc plugin, start a session with /dsh:run --session on the task <task>, then continue it with /dsh:run --resume on <follow-up>. Return the session identifier and the second response. Verify that the follow-up answer refers to content from the first turn.
Caveat. Session ids live only as long as the broker process, and stopping a mid-turn broker run discards in-memory sessions.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for cpj-dev/dsh-plugin-cc and "Keep a multi-turn DeepSeek session going across runs"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer