Describe allowed actions concretely
Hermes documents several protection layers, including user authorization, command approvals, file-write restrictions and container isolation. These controls answer different questions. An authorized chat participant may still encounter a blocked command; an isolated terminal does not decide whether a message should be sent to a customer.
Write a short action contract for the workflow. An inbox review might read one account, inspect a bounded date range and prepare a local queue. Drafting replies, changing labels and sending messages should be described separately. This makes the task easier to automate because agents can distinguish routine authorized work from a decision that belongs to the owner.
Use evidence to reduce interruptions
Choose an output location and a reviewable intermediate result. If the next step changes an external system, prepare the exact proposed change first. A person can then approve a concrete result rather than interpret a vague request to proceed. For a recurring read-only check, define the conditions that justify a notification and let the ordinary pass remain quiet.
Retain the account identity and action result with the task record, without saving secrets. When a workflow fails at a permission boundary, record the denied operation and required access instead of broadening all permissions. Restore only what that operation needs, then repeat a bounded check.
Scope and limits
These are workflow-design recommendations grounded in documented protection layers. They do not guarantee that a custom tool enforces every instruction. Unattended approval behavior varies by execution surface and configuration. Verify the relevant setting on the actual installation before relying on a headless task, and treat a refusal as evidence to diagnose rather than a reason to disable protections globally.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.
New Hermes Agent updates every day on X. Follow @HermesWatcher