What problem does it solve? Hermes splits its tools between a native Windows host and a Docker container, which causes confusing failures: tools vanish mid-session, localhost probes fail, paths don't resolve, and config changes silently don't apply. This Skill documents the verified topology so you can debug "works here but not there" problems correctly instead of chasing phantom bugs. ## Core Features & Use Cases - Host vs container split: Maps which tools run natively on Windows (web_search, browser_*, MCP servers) versus inside the Docker sandbox (terminal, read_file, execute_code), and the addressing rules that follow (host.docker.internal vs 127.0.0.1). - Filesystem and 9p guidance: Documents the /sandbox, /root, and /tmp mounts, the read-only skills mount, and the working pattern for avoiding wedged 9p sessions that poison the terminal. - Config failure forensics: Explains how a malformed terminal.docker_forward_env JSON value silently removes the entire container toolset and blocks MCP tool injection, with the correct cmd.exe and PowerShell quoting to fix it. - Use Case: After adding a new MCP server, its tools don't appear and terminal calls fail. This Skill tells you the session toolset is fixed at start, the gateway restart is insufficient, and to verify config JSON before opening a new chat session. ## Quick Start Load this skill whenever a task involves where code runs, where files land, reaching a service by host and port, missing dependencies, or a wedged terminal in this Hermes setup.
