Managed Scope
Managed Scope
Start with meaning, then move to detail.
This lesson explains Managed Scope as part of operating Hermes with explicit security boundaries. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Where it lives, Relocating the directory, Precedence, then verify failure modes and version compatibility.
You only need to know which files and accounts the agent may access.
A clear outcome before you read.
- Understand Managed Scope without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Approval & sandbox
- Approval pauses a sensitive action before execution; sandboxing limits impact if something goes wrong.
Administrator-pinned, user-immutable config and secrets via a system-level managed directory
What does the source say, and in what order?
- 01Where it lives
Start here to understand the core idea or structure.
- 02Relocating the directory
Read this after the foundation, then connect it to the previous step.
- 03Precedence
Read this after the foundation, then connect it to the previous step.
- 04Seeing what's managed
Read this after the foundation, then connect it to the previous step.
- 05Setting up a managed scope (administrators)
Read this after the foundation, then connect it to the previous step.
- 06Security model and limitations (v1)
Finish here to verify the result and special cases.
Copy only after you understand the effect.
/etc/hermes/
├── config.yaml # managed config layer (wins over ~/.hermes/config.yaml)
└── .env # managed env layer (wins over ~/.hermes/.env + shell)# Point managed scope at a custom directory (set by IT / the deployment, not the user)
export HERMES_MANAGED_DIR=/opt/org/hermes-policymodel:
default: org/standard-modelRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.