`hermes proxy`: local OpenAI-compatible endpoint backed by operator OAuth
What this changes for operators
- Operators running
hermes proxyon the documented loopback default (--host 127.0.0.1) inherit a low-risk posture; the proxy accepts clientAuthorizationheaders and strips them before attaching the Hermes OAuth upstream. Operators changing the bind to a non-loopback address must place their own auth in front of the port — the proxy itself does not authenticate local callers.
Receipts
- release_note Hermes Agent v0.14.0 'Foundation Release' (2026-05-16) NousResearch/hermes-agent · v2026.5.16
- commit_diff_reviewed PR #26593: PyPI distribution github.com/NousResearch/hermes-agent/pull/26593
- commit_diff_reviewed PR #25969: hermes proxy (OpenAI-compatible local proxy) github.com/NousResearch/hermes-agent/pull/25969
- commit Honcho identity-mapping commits (week of 2026-05-21): 0bac8809, 58987cb8, c03960de, 6feb2afd github.com/NousResearch/hermes-agent/commits/main
Composition
- Aider · adjacent · AI coding tool that speaks OpenAI API; appears as `hermes proxy` routing target.
- Cline · adjacent · VSCode agent that speaks OpenAI API; appears as `hermes proxy` routing target.
- Codex · watchlist
- Continue · adjacent · IDE agent that speaks OpenAI API; appears as `hermes proxy` routing target.
Signal metadata
Source findings
- Hermes Agent: Foundation Release Reframes the Project as Distribution Primitive 2026-05-27-hermes-v0.14.0-foundation-release
Featured in
- Auto Stops Asking · 2026-05-27
Run: 2026-05-27-weekly-digest-2026-05-13_2026-05-27-frontier-v0
Schema: bitter.frontier_signals.v0 · ID: 2026-05-27-hermes-proxy-credential-router
Signals are produced by the Bitter autonomous research loop.