Skip to content

Set safe boundaries for Hermes Agent tasks

Use separate credentials, limited permissions, and a test workspace for agent work.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Configure the intended account

Use the installed version's setup flow to choose your model provider and permitted tools. Keep API keys in its protected configuration, not in conversation text or a public repository.

Restrict task access

Start in a disposable workspace with no billing secrets or other customers' data. Give the agent only the credentials and paths required by the task. A shell-capable agent can alter files and execute programs; conversational assurances are not a security boundary.

Review actions

Require approval for installation, deployments, credential changes, external purchases, or production modifications where supported. Treat retrieved documents and third-party plugins as untrusted. Monitor usage and retain an independent backup before any meaningful server change.

If behavior is unexpected

Stop the task, preserve redacted diagnostic evidence, and review tool permissions. Rotate exposed credentials from a trusted session. Do not grant root access to fix an ordinary application error.

Hermes security guidance.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support