frozo-ai/dsh-worlds

README 摘要

dsh-worlds Run the agent's execution world inside a container — so it survives the harness that started it. DeepSeek Harness records this limitation in packages/terminal/terminal/README.md : "Sessions are process-local and are not restored after a harness restart ." The session log is durable. The computer the agent was working on is not — the shell dies with the harness, taking your cwd, exported variables, and background processes with it. dsh-worlds fixes that by moving the execution world into a Docker container. No CRIU, no microVMs: a container simply outlives its client. Why two plugins move everything From the harness's own architecture docs: "The existing dsh-bash-local , dsh-terminal-bash , and dsh-lsp-stdio need no forks . They delegate every execution-world operation to ctx.fs and ctx.subprocess ." Implement those two seams and Bash, persistent PTY terminals, LSP, and every file tool relocate into the container automatically. That is a deliberate architectural gift, and this project is what happens when you take it. Status Capability Checks Docker Engine API client + stream demux 11 unit + 12 live ctx.fs — all 12 methods 38 live Bounded collect buffers (offset-based, no…

分类