Files
deepseek-harness/packages/e2b/README.md
T

1.8 KiB

e2b/ — E2B remote runtime family

English | 中文

An experimental provider-composition POC that places the mutable coding world in one E2B Linux sandbox. The shared owner is separate from capability adapters so every remote provider awaits the same sandbox identity and lifecycle.

Package ctx key Role
e2b (@deepseek-ai/dsh-e2b) ctx.e2b Create or reconnect one sandbox, create its working/runtime directories, expose the shared SDK handle, and apply the configured kill/pause/leave disposition
fs-e2b (@deepseek-ai/dsh-fs-e2b) ctx.fs Implement the filesystem seam over E2B Filesystem APIs
subprocess-e2b (@deepseek-ai/dsh-subprocess-e2b) ctx.subprocess Implement managed process groups, stdio projection, and remote spill files over E2B Commands
pty-e2b (@deepseek-ai/dsh-pty-e2b) ctx.pty backend Run persistent interactive shells through E2B's byte PTY API
lsp-e2b (@deepseek-ai/dsh-lsp-e2b) ctx.lsp provider Run configured language servers and read query sources inside E2B
code-runtime-e2b (@deepseek-ai/dsh-code-runtime-e2b) ctx.codeRuntime Run model-written programs remotely while bridging bindings to the host

The existing dsh-bash-local needs no E2B-specific fork: it delegates process mechanics to ctx.subprocess, so replacing that provider places Bash in the same remote world. This boundary does not move the harness process, Cordis objects, model calls, agent/session state, session persistence, skills, protocol state, or E2B SDK buffers. The shared-runtime decision owns the POC boundary.