weijiafu14/dsh-remote-sandbox
Production-level remote execution world: pure JS sidecar in the E2B sandbox, single round trip to fs/subprocess, bounded process output, heartbeat keep-alive, crash transparent recovery (resume/recreate), tar workspace synchronization; fix two host assumptions in the official e2b POC. 43 tests (including 6 real machine E2E) all green
A production-grade remote execution world for DeepSeek Harness: it moves ctx.fs and ctx.subprocess into an E2B sandbox that survives crashes, stays alive under load and keeps your workspace in sync. The README positions it against the official @deepseek-ai/dsh-e2b proof-of-concept, which its own docs describe as deliberately ephemeral — a five-minute sandbox lifetime, complete process output held in host memory, and no host-workspace upload or sync. This suite adds heartbeat keep-alive so the sandbox lives as long as the task, transparent recovery from connection drops by resuming the paused sandbox with its disk retained, recreate-and-restore from the last synced snapshot after a hard crash, and host-workspace synchronization. Its dsh-sandbox-keeper configuration covers the API key (never forwarded into the sandbox), the E2B template, the in-sandbox cwd and host workspace mapping, and a pause deadline the heartbeat pushes forward.
Install
dsh plugin --profile <name> add dsh-remote-sandboxREADME Install section quoted verbatim (replace <name>); the README's next line exports the required E2B_API_KEY (export E2B_API_KEY=e2b_...). Registry-verified live 2026-09-15: dsh-remote-sandbox latest 0.1.0 (published 2026-08-14); the registry entry carries no repository field, so npm ownership is disclosed but not asserted.
Compatibility
The README labels this a third-party plugin suite, not affiliated with DeepSeek, MIT licensed. The bundle layers over dsh-base: it disables the local subprocess and fs-sandbox providers and inserts the keeper plus the remote providers, with Bash, terminal and LSP composing above them unchanged. It requires an E2B account and API key, and the README warns upstream dsh is in developer preview with loosely pinned peer versions that may need bumping.
Details
- Repo: weijiafu14/dsh-remote-sandbox
- Category: Coding & Development
- Stars: 0
- Version: npm dsh-remote-sandbox 0.1.0 (registry-verified 2026-09-15)
- Last push: 2026-08-14
- First seen: 2026-08-13
Recent updates
The README documents the design and configuration rather than a release-by-release changelog; the latest version on the registry when checked on 2026-09-15 was 0.1.0.
FAQ
- How do I install it?
- The README's command is dsh plugin --profile <name> add dsh-remote-sandbox, followed by exporting E2B_API_KEY.
- How is it different from the official dsh-e2b plugin?
- Per the README, the official package is a POC with a fixed five-minute sandbox lifetime and no workspace sync; this suite adds heartbeat keep-alive, recovery from connection drops, recreate-and-restore after a crash, and host-workspace synchronization.
- Is the API key exposed to the sandbox?
- No — the README states the dsh-sandbox-keeper apiKey (defaulting to $E2B_API_KEY) is never forwarded into the sandbox.
Alternatives
030611/dsh-context-provenance · 030611/qiushi-dsh-evidence-audit · 0x3fffff/dsh-desktop-launcher