AngelosZou/dsh-multi-folder
Secondary working directories for a DSH project: the agent keeps the primary workspace as cwd and gains equal read/write/exec permissions on configured secondary directories, configurable from the session header and the new-session page.
dsh-multi-folder gives one DeepSeek Harness project (workspace) a set of secondary working directories — edit a source repo, a test repo, and a docs repo side by side without leaving the primary workspace. The agent's core cwd and other core attributes keep pointing at the primary workspace, while under Workspace Write mode it gains the same permissions on the configured secondary directories (enforced by re-rooting the session's sandbox policy, so read-only still denies and danger-full-access still allows). The directory list is injected into the system prompt per session assembly; configuration changes notify the agent through a non-interrupting message queue delivered at the next message boundary only when the directory set actually changed; and everything is configurable before the session starts via a sessionless remote API from the session-creation page.
Install
dsh plugin --profile web add dsh-multi-foldernpm package dsh-multi-folder 0.1.6 (registry-verified 2026-08-24). Link the repository into a DSH profile: dsh plugin --profile web add dsh-multi-folder. Then restart the DSH backend (host composition loads at process start) and refresh the browser page (the client bundle is served no-cache). A Multi-folder button appears in the session header and on the session-creation page. Node.js >= 20.
Compatibility
DeepSeek Harness web profile composed from @deepseek-ai/dsh-base + @deepseek-ai/dsh-web-app. Node.js >= 20. Workspace Write mode grants the agent the same read/write/edit/execute permissions on configured secondary directories as on the primary workspace — enforced by re-rooting the session's own sandbox policy, so every mode keeps its semantics (read-only still denies, workspace-write allows, danger-full-access allows). Directory list is injected into the system prompt and re-rendered per session assembly. No new tools — framework-level tool-pipeline interception plus a UI-level session-scoped header entry. MIT.
Details
- Repo: AngelosZou/dsh-multi-folder
- Category: Tools & Capabilities
- Stars: 6
- Version: npm package dsh-multi-folder 0.1.6 (registry-verified 2026-08-24)
- Last push: 2026-08-22
- First seen: 2026-08-14
Recent updates
The current English README documents: the secondary-working-directories concept, requirements (Node >= 20, dsh-base + dsh-web-app profile), install (dsh plugin add + restart + refresh), usage (Multi-folder button on session header and creation page, popover panel, add/remove directories), the workspace-write sandbox re-rooting semantics, system-prompt injection, the non-interrupting config-change notification queue, and the sessionless remote API.
FAQ
- Do secondary directories change the agent's cwd?
- No — the agent's core cwd and every other core attribute keep pointing at the primary workspace; secondary directories are additional writable locations.
- How are permissions enforced?
- Under Workspace Write mode the session's sandbox policy is re-rooted so the agent gets the same read/write/edit/execute permissions on secondary directories as on the primary — read-only still denies, workspace-write allows, danger-full-access allows.
- How does the agent learn about new directories?
- The directory list is injected into the system prompt and re-rendered per session assembly; config changes are announced through a non-interrupting message queue delivered at the next message boundary only when the set actually changed.
Alternatives
huey1in/trio · lanyun077/dsh-project · YiRan0/dsh-mobile-glass