Local vs Remote Terminal Backends

When Hermes runs commands, the environment matters. A command may run on the local machine or inside a configured backend such as Docker, SSH, or another managed environment.

Why this matters

Paths, installed packages, OS details, network access, and credentials can differ between environments. A file that exists on your Mac may not exist inside a container. A command that works locally may fail remotely.

What to check

Use safe discovery commands when needed:

pwd
whoami
uname -a
python --version

Also confirm the working directory before running project-specific commands.

File tools and terminal tools

In a remote backend configuration, file tools may operate in that backend environment rather than the host. Treat the active backend as the source of truth for what Hermes can actually touch.

Good operator habit

Do not assume a repo path. If the user gives an exact path, use it. If not, discover the path before issuing repo-specific commands.

Verification

After changing backend configuration, run a harmless command and read a known test file. Confirm that both terminal and file tools are pointed at the intended environment before editing or deploying.