Resources and Update Tracking
Resources and Update Tracking
Section titled “Resources and Update Tracking”Hermes changes quickly, and second-hand tutorials can age fast. For installation, providers, tools, gateway, and automation questions, start with official docs, PyPI, GitHub releases, and source before community posts.
Most useful sources
Section titled “Most useful sources”| What to confirm | Start here |
|---|---|
| Install paths and platform differences | Installation |
| First run and model setup | Quickstart |
| Python requirement and package version | PyPI hermes-agent |
| Latest release | GitHub releases |
| Full documentation index | llms.txt |
| FAQ and common failures | FAQ |
| Source and issues | GitHub repository |
When to re-verify
Section titled “When to re-verify”Do not rely on old notes when:
- Writing team install docs.
- Pinning or upgrading a version.
- Enabling gateway, cron, or API server.
- Provider, model, OAuth, or pricing behavior changes.
- Production automation suddenly fails.
- Writing public technical docs or tutorials.
Version baselines need dates. For example: “Checked PyPI on 2026-05-25: hermes-agent 0.14.0, Python >=3.11.” A version claim without a date loses value quickly.
Official docs by topic
Section titled “Official docs by topic”What to record locally
Section titled “What to record locally”Do not mirror the official docs into your project. Record only the decisions that matter to your setup:
Hermes version:Install method:Provider:Model:Enabled toolsets:Gateway platforms:Cron jobs:Skills used:Security boundaries:Last verified:Owner:That makes future upgrades about known dependencies, not archaeology through chat history.