dsh-shell-wsl

LIMITATIONS

Known limitations

- **No interactive PTY / persistent shell**: every call is a brand-new container (matching the official fresh-shell semantics; apt installs, `cd` and variables don't survive across calls). If you need a persistent shell / PTY, extend via the official `terminal` capability family — this plugin deliberately keeps the one-shot semantics. - **Occasional timeouts on short commands**: usually a first-time image pull; pre-warm with `docker pull` (see §1). - **Mount I/O is slower than native Windows**: inherent to Docker Desktop file sharing (9p / grpcfuse). - **`rm -rf` inside the mount is not blocked by ACL**: the container can only see the mounted volume and has no write access to the system drive — the same risk surface as workspace-write mode. - **danger-full-access is equivalent to workspace-write**: a container executor cannot grant host-wide access; both mount read-write (see §6). - **No `docker` / `wsl.exe` inside the container, on purpose**: do Docker/WSL troubleshooting in **the user's own terminal** (probing from inside the agent sandbox is unreliable too). - **Private image registries**: the docker-cli transport shares Docker Desktop credentials; the wsl transport needs a credential helper configured inside the distro. - **Chinese / UTF-8 output**: the container forces `LANG=C.UTF-8`; rendering is normal.