Provider Runtime Resolution
Hermes has a shared provider runtime resolver used across: CLI gateway cron jobs ACP auxiliary model calls Primary implementation: — credential resolution, — pr
Hermes has a shared provider runtime resolver used across: Primary implementation: in returns a for a given provider id. calls this at resolution time to get the canonical , priority list, , and without needing to duplicate that data in multiple files. …
What this page covers
- Resolution precedence
- Providers
- Output of runtime resolution
- Why this matters
- OpenRouter and custom OpenAI-compatible base URLs
- Native Anthropic path
- OpenAI Codex path
- Auxiliary model routing
- Fallback models
- How it works internally
- What does NOT support fallback
- Test coverage
- Related docs
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
More in Developer Guide
Contributing
Thank you for contributing to Hermes Agent! This guide covers setting up your dev environment, understanding the codebase, and getting your PR merged. Contribut
Architecture
This page is the top level map of Hermes Agent internals. Use it to orient yourself in the codebase, then dive into subsystem specific docs for implementation d
Agent Loop Internals
The core orchestration engine is 's class — a large file that handles everything from prompt assembly to tool dispatch to provider failover. Core Responsibiliti
Prompt Assembly
Hermes deliberately separates: cached system prompt state ephemeral API call time additions This is one of the most important design choices in the project beca
Context Compression and Caching
Context Compression and Caching Hermes Agent uses a dual compression system and Anthropic prompt caching to manage context window usage efficiently across long
Gateway Internals
The messaging gateway is the long running process that connects Hermes to 20+ external messaging platforms through a unified architecture. Key Files File Purpos