# witcheer's Wingtips #78: approvals.smart_policy, your own rules for the command reviewer

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/78  
Published: 2026-09-20  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/78-smart-policy/) · [On X](https://x.com/witcheer/status/2101606053800456228) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/configuration#custom-smart-approval-policy)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/78-smart-policy.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Configuration](https://hermes-agent.nousresearch.com/docs/user-guide/configuration#smart-approvals)


when Hermes Agent wants to run a terminal command that looks risky, a second model reviews it first. it reads the command and answers with one word: approve, deny, or escalate, which means ask you.

this key lets you add your own rules to that reviewer's instructions.

"always escalate anything that modifies /etc."
"approve docker compose restarts in ~/deploys, they are routine here."

your rules are read as instructions from you, never as part of the command it is judging.

```yaml
approvals:
  smart_policy: |
    Always ESCALATE commands that modify anything under /etc.
```

empty by default. the reviewer itself is on by default (`approvals.mode: smart`).

docs: [https://hermes-agent.nousresearch.com/docs/user-guide/configuration#smart-approvals](https://hermes-agent.nousresearch.com/docs/user-guide/configuration#smart-approvals)