deepseek-web-import
通过设置页面 UI 将 chat.deepseek.com 对话导入 DeepSeek Harness，作为可恢复的会话。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:wpc0323/deepseek-web-import#7727f18e3996713dec1b7046d07897c19efed5aeDeepseek Web Import 以 deepseek-web-import 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Import your chat.deepseek.com conversation history as real DeepSeek Harness (DSH) sessions: each import appears in the sidebar workspace list, opens with its full history, and can be continued with any model.
This is an installable DSH plugin bundle (
dsh.bundlemanifest: a host half plus a web client half), installed withdsh plugin add. See Install below.
userToken and fetch the conversation directory in one click (titles + dates only; transcripts are fetched on import)cannot prepare session while it is live)~/.dsh/sessions/<workspace>/ and survive a DSH restartvalue field from a userToken automatically (accepts the {"value":"...","__version":"0"} form)Refresh the page (F5) after importing a conversation so the sidebar shows the new session immediately.
Without a refresh the new session may only appear after the next session-list refresh or reconnect.
The plugin declares dsh.bundle (see package.json), so it installs with dsh plugin add:
dsh plugin add wpc0323/deepseek-web-import
After installing, restart DSH; Settings → DeepSeek Chat Import then appears. In this repository
lib/index.jsis the host half (same-origin JSON routes) andlib/client.jsis the web client half (the settings-page UI); they talk over thewebServerroutes andfetch.
userToken → Save.
F12 → Application → Local Storage → copy the userToken value.value field itself, so pasting the whole entry is fine.1. Open Settings → DeepSeek Chat Import
2. Paste the userToken → Save (the status turns "configured")
3. Click "Load conversations" → your DeepSeek conversations appear (title + date)
4. On the "sharp load failure fix" row, pick the workspace dsh-work → click "Import as session"
5. Refresh the page → "sharp load failure fix" appears in the sidebar → open it and continue the conversation
An import writes to persistence only (
sessionPersistence) and never enters the live store, which is why an imported session can be opened and continued normally (it never reportscannot prepare session while it is live).
That failure is a DSH recovery-cursor bug of its own (session/end-seed is appended separately by a live session, and the post-restart cursor misses it, so a seq gets reused); it is unrelated to this plugin, whose bulk write happens to avoid the trigger. Symptoms, root cause, and the repair are in docs/TROUBLESHOOTING.md (Chinese).
Every DSH release writes one session format (v0…v4). The plugin adapts to the running build. Measured matrix:
| DSH version | Session format | Status |
|---|---|---|
| 0.1.0-rc.7 – 0.1.2-rc.1 | v0 | ✅ verified against the real backend |
| (unreleased) | v1 | ✅ modeled as v0 + runtime dialect evidence |
| 0.1.3-alpha.2 | v2 | ✅ verified against the real backend |
| 0.1.5-alpha.1 – 0.1.6-alpha.2 | v3 | ✅ verified against the real backend |
| 0.1.7-alpha.1+ (including desktop 0.2.0-rc.2) | v4 | ✅ verified against the real backend |
How each row was verified, and where the evidence comes from, is in docs/COMPATIBILITY.md (Chinese). npm test runs the unit tests; sh test/matrix.sh runs the full matrix.
lib/index.js (host half) registers same-origin JSON routes (/__deepseek-web-import/*) on DSH's webServer; lib/client.js (web client half) calls them with fetch from the settings page. No dynamic-plugin machinery is involved, so the plugin stays installed across restarts.GET /api/v0/chat_session/fetch_page?count=100GET /api/v0/chat/history_messages?chat_session_id=<uuid>turn/start → user/message → step/start → assistant/message → step/end → turn/end, surface events carrying surfaceOp: "append", plus session/title and session/end-seed), written to persistence only (v0/v1 through create(meta) + append(id, events), v2+ through the write handle returned by create(header)), and then attached to the chosen workspace with workspace.attachSession — the session never enters the live store, which is what makes it openable and continuable. A history that ends with an unanswered user question keeps its unclosed turn; DSH closes it with interrupted when the session is opened.fragments (REQUEST/RESPONSE/THINK). A user question comes from REQUEST; an answer uses RESPONSE as the text and THINK as a reasoning block. Event times come from the message's inserted_at.web.fetch cannot carry custom headers, so the plugin runs Node through the subprocess service and sends the request with Authorization: Bearer. The request spec (including that header) travels on the child's stdin, so it never shows up in ps//proc. Certificates are verified first; only a certificate-class failure (an environment whose TLS is intercepted by a proxy or antivirus) retries once without verification and reports insecureTls (one line in the DSH log, visible in Diagnostics) instead of degrading silently. The child bounds the streamed response by characters (~2M) and by bytes (6MB) and reports instead of buffering a huge response into memory.userToken route is the only one.fetch_page response carries only chat_sessions + has_more, with no usable cursor field (cursor/lte_cursor have no effect), so beyond 100 you get the latest 100.userToken expires after some hours to days; copy and save a fresh one when it does.dsh plugin add and stays installed across DSH restarts.TOOL_SEARCH/TOOL_OPEN fragments) and message status (an INCOMPLETE answer cut off while generating) are not preserved: web search has no DSH event to map onto, so only the text and reasoning are imported; an interrupted answer keeps whatever text/reasoning it had.too_large rather than being silently truncated).SYSTEM/TOOL, …) are ignored.history_messages (it does not resolve parent_id branches): if DeepSeek returns sibling branches for an edit/regenerate, they are imported as two consecutive turns.userToken in a conversation, issue, or repository.too_largectx.locale), so it follows the DSH/browser language and falls back to English for unregistered languages (German, say). Without a locale service the module resolves the browser language itself.credentials service ($DSH_HOME/.credentials.yaml); it is never written into a session or the settings document.