Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Context References

Type followed by a reference to inject content directly into your message. Hermes expands the reference inline and appends the content under an section. Support

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/context-references

Type followed by a reference to inject content directly into your message. Hermes expands the reference inline and appends the content under an section. Support

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Supported References
  2. Usage Examples
  3. CLI Tab Completion
  4. Line Ranges
  5. Size Limits
  6. Security
  7. Sensitive Path Blocking
  8. Path Traversal Protection
  9. Binary File Detection
  10. Platform Availability
  11. Interaction with Context Compression
  12. Common Patterns
  13. Error Handling

Section map

Supported References

Maps supported references to the Core Features documentation path, with the source page reserved for exact commands and updates.

Usage Examples

Maps usage examples to the Core Features documentation path, with the source page reserved for exact commands and updates.

CLI Tab Completion

Maps cli tab completion to the Core Features documentation path, with the source page reserved for exact commands and updates.

Line Ranges

Maps line ranges to the Core Features documentation path, with the source page reserved for exact commands and updates.

Size Limits

Maps size limits to the Core Features documentation path, with the source page reserved for exact commands and updates.

Security

Maps security to the Core Features documentation path, with the source page reserved for exact commands and updates.

Sensitive Path Blocking

Maps sensitive path blocking to the Core Features documentation path, with the source page reserved for exact commands and updates.

Path Traversal Protection

Maps path traversal protection to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Supported References, Usage Examples, CLI Tab Completion, Line Ranges, Size Limits. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: context, references, followed, reference, inject. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for context references before applying exact upstream commands.

Verify firstSupported References

Open the source anchor for Supported References and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Supported References; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Usage Examples if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page