dsh-chat-projects
ChatGPT Projects 风格的 DeepSeek Harness 聊天整理工具：在工作区（项目）之间移动会话，并将未分组的聊天归入其所属项目。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Tzh0109/dsh-chat-projects#a97a093336a5dbd0f55835956a1c603ee2596ba5Chat Projects 以 dsh-chat-projects 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
ChatGPT Projects style chat organization for DeepSeek Harness (DSH): move an existing session between workspaces (projects) from the session row menu, or file ungrouped sessions back into the project their recorded directory belongs to — without replacing the native sidebar.
DSH binds a session to its workspace at creation time and ships no "move to another project" operation. This plugin adds exactly that missing capability: project creation, rename, reorder and delete stay native.
<DSH_HOME>/dsh-chat-projects/pending-moves.json);
it runs automatically on the next DSH start, before any agent resumes. The
dialog can cancel the queued move.0.2.1-rc.x) with its bundled runtime — the Host half needs
Node's built-in Zstandard API (Node >= 22.15; DSH ships 24.x).react comes from the
DSH client baseline).Use the CLI that ships with DSH desktop. The npm package is dsh-chat-projects
(the GitHub repository keeps its original name, dsh-projects):
# from npm (easiest)
dsh plugin --profile desktop add dsh-chat-projects
# from GitHub (repository name is dsh-projects)
dsh plugin --profile desktop add github:Tzh0109/dsh-projects
# or from a local checkout (development)
dsh plugin --profile desktop add "link:C:\path\to\dsh-chat-projects"
If dsh is not on PATH, use the bundled entry point
<DSH install>\resources\runtime\cli\bin\dsh.cmd.
Restart the DSH desktop app once — the Host half needs a restart. After that,
edits to lib/client.js hot-reload through the client HMR channel.
Uninstall:
dsh plugin --profile desktop remove dsh-chat-projects
The dialog footer also offers File ungrouped sessions (N), which only touches ungrouped sessions whose recorded directory is already a project (archived sessions are skipped).
In DSH a session belongs to a project because three things agree:
| # | Fact | Location |
|---|---|---|
| 1 | workspace record's ordered sessionIds | ~/.dsh/storages/workspace.json |
| 2 | immutable cwd in the session header | frame 0 of the session log |
| 3 | log directory, a pure function of that cwd | ~/.dsh/sessions/--<project key>--/<session id>/session.v4.jsonl.zstd |
They agree only at creation time, and DSH exposes a (restricted) write entry
point only for #1 (attachSession / detachSession on the workspace entity).
This plugin therefore performs a real move:
cwd, keeping every committed event frame byte-for-byte;stat + one event page), and
roll back automatically on failure;workingDirectory so list titles
and statistics survive the move.header.cwd is also the workspace-write sandbox root, so a moved session's
tool boundary follows it to the new project.
The plugin refuses instead of forcing a move when:
workspace/session-activity reports
turns, subagents, jobs or schedules);origin: subagent);cwd;<DSH_HOME>/dsh-chat-projects/journal.json (removed on success)<DSH_HOME>/dsh-chat-projects/backups/<DSH_HOME>/.dsh-chat-projects-trash/ (same-volume rename,
removed on success)On startup the plugin reads the journal: old-moved is rolled back,
new-written / verified are completed. If automatic recovery fails the
journal is kept and a warning is logged, and the trash directory can be renamed
back manually.
npm test after an upgrade, and try a throwaway
session first.workspace-write sandbox: the new project directory needs DSH's sandbox
authorization (a DACL on Windows). With danger-full-access this is moot.git clone https://github.com/Tzh0109/dsh-projects
cd dsh-projects
npm test # node --test test/core.test.mjs
The suite is self-contained: it generates synthetic checksummed zstd session logs and drives the mover with fake persistence/registry services (path derivation, header rewriting, move, busy refusal, rollback, bulk organizer and queued moves). No local DSH data is read.
Layout:
dsh-chat-projects/
├─ package.json # dsh.bundle.patch + dsh.client declarations
├─ cordis.patch.yml # Host-half loader entry
├─ lib/
│ ├─ index.js # Host entry: same-origin JSON API
│ ├─ mover.js # moving engine: path codec, zstd header rewrite,
│ │ # accounting, rollback, crash recovery
│ └─ client.js # browser half: session row menu + project dialog
└─ test/core.test.mjs # offline tests
Host API (same-origin, behind DSH's connection trust fence):
GET /plugins/dsh-chat-projects/api/state?session=<id>
POST /plugins/dsh-chat-projects/api/move {"sessionId": "...", "targetWorkspaceId": "..." | null}
POST /plugins/dsh-chat-projects/api/queue {"sessionId": "...", "targetWorkspaceId": "..." | null}
POST /plugins/dsh-chat-projects/api/unqueue {"sessionId": "..."}
POST /plugins/dsh-chat-projects/api/organize {}
MIT