Context References
Context References
Start with meaning, then move to detail.
This lesson explains Context References 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 Supported References, Usage Examples, CLI Tab Completion, 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 Context References 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.
- Approval & sandbox
- Approval pauses a sensitive action before execution; sandboxing limits impact if something goes wrong.
Inline @-syntax for attaching files, folders, git diffs, and URLs directly into your messages
What does the source say, and in what order?
- 01Supported References
Start here to understand the core idea or structure.
- 02Usage Examples
Read this after the foundation, then connect it to the previous step.
- 03CLI Tab Completion
Read this after the foundation, then connect it to the previous step.
- 04Line Ranges
Read this after the foundation, then connect it to the previous step.
- 05Size Limits
Read this after the foundation, then connect it to the previous step.
- 06Security
Read this after the foundation, then connect it to the previous step.
- 07Sensitive Path Blocking
Read this after the foundation, then connect it to the previous step.
- 08Path Traversal Protection
Read this after the foundation, then connect it to the previous step.
- 09Binary File Detection
Read this after the foundation, then connect it to the previous step.
- 10Platform Availability
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Review @file:src/main.py and suggest improvements
What changed? @diff
Compare @file:old_config.yaml and @file:new_config.yaml
What's in @folder:src/components?
Summarize this article @url:https://arxiv.org/abs/2301.00001Check @file:main.py, and also @file:test.py.@file:src/main.py:42 # Single line 42
@file:src/main.py:10-25 # Lines 10 through 25 (inclusive)Read 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.