Hermes Agent cannot read local files while running in Docker. The most common reason is that the model is not working, but that the host directory is not properly mounted into the container, or the file/terminal capability is not enabled in the current toolset of Hermes Agent. The container naturally cannot see all the host files unless you explicitly map the directory into it.
Check three things first
- Docker mount: Confirm that there is a mapping like
-v /host/path:/workspacein the compose ordocker run_.Path in the container: The one you access in the Hermes Agent is/workspace, not the host's/Users/you/project.- Whether the tool is enabled: Check the
hermes toolsor platform tool configuration to ensure that file / terminal related capabilities are not turned off.
Why can it be read locally? Docker can't?local backend is executed on your host computer and can naturally read files for which the current user has permissions;Docker backend is executed in a container isolation environment, and only files in the image and mounted directories can be seen. The Hermes Agent's security design inherently encourages this isolation, at the expense of having to explicitly tell it which directories are visible.Recommended troubleshooting command
Let Hermes Agent executepwd,ls -la /workspace,whoamiin the container first, and confirm the path and permissions. If the directory exists but cannot be written to, check the host permissions, SELinux/AppArmor, and Docker Desktop file sharing settings. If the directory does not exist at all, it means that it has not been mounted into the container.Don't hang the entire home or root directory in it to save trouble. A better practice is to only mount the current project directory and use a read-only mount to handle data that does not need to be written.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
