hermes-wslc-sandbox.yaml 1.7 KB

1234567891011121314151617181920
  1. name: hermes-wslc-sandbox
  2. repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
  3. sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
  4. subdir: wslc-sandbox
  5. version: "0.1.0"
  6. description: "Run Hermes' terminal, file and execute_code tools in a Linux container on Microsoft's WSL Containers (wslc) runtime, so Windows users who run WSL Containers get a sandbox without Docker Desktop. Disclosure — the plugin spawns the wslc CLI (one short-lived process per command, plus one long-lived container per environment) and every call runs inside that container; containers have outbound network access unless docker_network is false; persistent sandboxes are left stopped on disk until removed; host environment variables enter the container only when named in docker_forward_env, and only paths listed in docker_volumes are bind-mounted. wslc rejects --cap-drop, --security-opt, --pids-limit, --init and --storage-opt, so this sandbox is not capability-dropped the way the Docker backend's is, container_disk is reported but not enforced, and dangerous-command approval deliberately stays enabled for this backend. The plugin reads no credentials, stores none, and makes no network calls of its own."
  7. maintainer: Yicheng-Mark
  8. tier: community
  9. category: tools
  10. requires_hermes: ">=0.21.3"
  11. docs_url: https://github.com/Yicheng-Mark/hermes-windows-plugins/tree/main/wslc-sandbox
  12. platforms: [windows]
  13. known_issues:
  14. - "container_disk is reported but not enforced: wslc has no --storage-opt."
  15. - "No capability dropping: wslc rejects --cap-drop and --security-opt, so dangerous-command approval stays enabled."
  16. capabilities:
  17. provides_tools: []
  18. provides_hooks: []
  19. provides_middleware: []
  20. requires_env: []