DSH Code Runtime Container
Container-isolated backend for the DeepSeek Harness code-execution seam: Code Mode programs run in a fresh container with no network, a read-only rootfs, and kernel-enforced memory, CPU, and pid ceilings.
Project overview
A container-isolated backend for the DeepSeek Harness code-execution seam (ctx.codeRuntime). Code Mode programs run in a fresh container with no network, a read-only root filesystem, every capability dropped, and kernel-enforced memory, CPU, and pid ceilings. Why
The seam declares three well-known isolation substrates and ships one. From @deepseek-ai/dsh-code-runtime's own README: Only the worker-thread backend ships — 'process'/'container' are declared well-known isolation values with no implementation; a hard security boundary awaits a container backend.
And the shipped backend is equally explicit about its posture: Containment, not a security boundary: trust posture is bash-equivalent by design.