Environment Variables
Environment Variables Reference All variables go in . You can also set them with . LLM Providers Variable Description OpenRouter API key (recommended for flexib
- Section
- Reference
- Source
- hermesbible.com/docs/reference/environment-variables
Environment Variables Reference All variables go in . You can also set them with . LLM Providers Variable Description OpenRouter API key (recommended for flexib
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- LLM Providers
- Provider Auth (OAuth)
- Tool APIs
- Langfuse Observability
- Nous Tool Gateway
- Terminal Backend
- SSH Backend
- Container Resources (Docker, Singularity, Modal, Daytona)
- Persistent Shell
- Messaging
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
- LLM Providers
- Provider Auth (OAuth)
- Tool APIs
- Langfuse Observability
- Nous Tool Gateway
- Terminal Backend
- SSH Backend
- Container Resources (Docker, Singularity, Modal, Daytona)
- Persistent Shell
- Messaging
- Web Dashboard & Hermes Desktop
- Microsoft Graph (Teams Meetings)
- Microsoft Graph Webhook Listener
- Teams Meeting Summary Delivery
Section map
LLM Providers
Maps llm providers to the Reference documentation path, with the source page reserved for exact commands and updates.
Provider Auth (OAuth)
Maps provider auth (oauth) to the Reference documentation path, with the source page reserved for exact commands and updates.
Tool APIs
Maps tool apis to the Reference documentation path, with the source page reserved for exact commands and updates.
Langfuse Observability
Maps langfuse observability to the Reference documentation path, with the source page reserved for exact commands and updates.
Nous Tool Gateway
Maps nous tool gateway to the Reference documentation path, with the source page reserved for exact commands and updates.
Terminal Backend
Maps terminal backend to the Reference documentation path, with the source page reserved for exact commands and updates.
SSH Backend
Maps ssh backend to the Reference documentation path, with the source page reserved for exact commands and updates.
Container Resources (Docker, Singularity, Modal, Daytona)
Maps container resources (docker, singularity, modal, daytona) to the Reference documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Reference 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: LLM Providers, Provider Auth (OAuth), Tool APIs, Langfuse Observability, Nous Tool Gateway. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: environment, variables, reference, providers, variable. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for environment variables before applying exact upstream commands.
Open the source anchor for LLM Providers and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Reference, then open the linked source page for exact current syntax.
- Start with the source section for LLM Providers; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Provider Auth (OAuth) if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
Set provider, token, and retry limits before scaling the workflow beyond a single test run.
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