Sora233/dsh-extra-workspaces
Extra writable workspaces for workspace-write mode at global, per-workspace and per-session scope, with first-run toolchain cache detection.
Adds directories that get the same write access as a session's primary workspace under workspace-write mode — for confined shell commands and for the write/edit tools from one list, so the shell and the file tools can never disagree about what is writable. The list exists at three scopes whose union applies to each confined call: global (every session, edited on the plugin's settings card), workspace-level (every conversation whose project directory is that workspace, edited in the session header) and session-only. First run probes the toolchains and imports what they report — Go's build cache and module cache, Cargo and rustup homes, uv, pip, npm, pnpm, Yarn, Bun and Deno locations — with nested directories collapsed to the outermost and anything already writable dropped. Go is deliberately narrow: $GOBIN is not granted, so go install is still denied. Provider rows still gate on mode, so read-only keeps denying even a listed directory and danger-full-access still bypasses the list entirely.
Install
dsh plugin --profile web add dsh-extra-workspacesThe README's CLI line, which needs one documented follow-up: the package must also be listed in that profile's package.json under dsh → profile → bundles, after the base bundles (the Settings → Plugins → Add route does both steps for you). This is a bundle rather than a single plugin row — its patch disables the stock sandbox and filesystem rows by id and inserts its own in their place — so composing it as one row is wrong. Restart the profile, then reload the page: the host half is composed at boot while the client half is served on page load.
Compatibility
Node.js >= 22 and DSH >=0.2.1-rc.2 <0.3.0, tested by the author on both 0.2.1-rc.2 and 0.2.1-rc.3. Support is per platform and stated exactly: Linux Landlock and bubblewrap are supported, macOS Seatbelt is implemented and unit-tested but was not run on a real Mac, and Windows gets no widening at all because the ACL runner accepts a single workspace SID — stock confinement is left as it was there. Do not compose it over a container, microVM or remote executor, or over the deliberately unconfined dsh-fs-local, because its rows replace the sandbox and filesystem services. Failure is designed to be loud and closed: a version mismatch or a moved hook refuses the bundle and leaves those services absent, rather than quietly granting nothing or falling back to an unconfined sandbox.
Details
- Repo: Sora233/dsh-extra-workspaces
- Category: Infrastructure & Deployment
- Stars: 1
- Version: 0.3.0 (npm)
Alternatives
harryopo/dsh-cloud-workspaces · GooDAnDReaDY/dsh-remote-workspace · DobyChao/dsh-workspace-enhancement