Skip to content

docs: document Hermes config destinations #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dorukardahan merged 1 commit into from
Aug 13, 2026
Merged

docs: document Hermes config destinations #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion examples/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,14 @@
# ZeroAPI v3 Configuration Examples

Pick the example that matches your provider subscriptions. Each file is a ready-to-use `zeroapi-config.json` policy snapshot — copy it to `~/.openclaw/zeroapi-config.json`.
Pick the example that matches your provider subscriptions. Each file is a ready-to-use `zeroapi-config.json` policy snapshot. OpenClaw users can copy it to `~/.openclaw/zeroapi-config.json`.

The same example files can seed the [Hermes adapter](../integrations/hermes/README.md). Hermes discovers the policy in this order:

1. the path set by `ZEROAPI_CONFIG_PATH`, when present;
2. `~/.hermes/zeroapi-config.json`;
3. `~/.openclaw/zeroapi-config.json` as a fallback.

The shared policy file does not replace either host's provider, credential, or model configuration. Hermes still owns those runtime settings, just as OpenClaw keeps its runtime settings in `~/.openclaw/openclaw.json`.

If you are using OpenClaw from Slack, Telegram, WhatsApp, Matrix, Discord, or another chat channel, start with:

Expand Down