ZenMux for Hermes Agent
Use ZenMux models in Hermes Agent with browser OAuth. The plugin provides:
- OAuth 2.0 Authorization Code + PKCE login
- access/refresh-token storage in Hermes' credential pool
- serialized refresh-token rotation
- a live ZenMux model catalog in
hermes model - direct use of full ZenMux model slugs
- OpenAI-compatible chat-completions transport
Requirements
- Hermes Agent with the declarative OAuth PKCE plugin API (main at or after
3e67877e1b). - Python 3.11 or newer when installing from PyPI.
- A browser for the initial ZenMux authorization.
The package includes ZenMux's dedicated public OAuth client for Hermes. No client secret is bundled or required.
Installation
Option A: install from GitHub (recommended)
hermes plugins install ZenMux/hermes-plugin --enable
hermes gateway restart
For a reproducible installation, pin an immutable commit shown on the latest release page:
hermes plugins install ZenMux/hermes-plugin --ref <40-character-commit> --enable
If another process manager owns the gateway, restart it there instead:
pm2 restart hermes-gateway --update-env
Option B: install from PyPI
Install into the same Python environment as Hermes:
~/.hermes/hermes-agent/venv/bin/python -m pip install zenmux-hermes-plugin
hermes plugins enable zenmux
hermes gateway restart
A system-wide Hermes installation may instead use:
python3 -m pip install zenmux-hermes-plugin
hermes plugins enable zenmux
Option C: install as a filesystem provider
HERMES_HOME="${HERMES_HOME:-$HOME/.hermes}"
mkdir -p "$HERMES_HOME/plugins/model-providers"
git clone https://github.com/ZenMux/hermes-plugin.git \
"$HERMES_HOME/plugins/model-providers/zenmux"
Restart Hermes after installation.
Sign in to ZenMux
hermes auth add zenmux
hermes auth status zenmux
Hermes opens ZenMux. Select an account and billing method, then approve access. Useful commands:
hermes auth list zenmux
hermes auth refresh zenmux
hermes auth logout zenmux
Access and refresh tokens are stored by Hermes in its credential pool, not in
the plugin. zenmux.json contains only the public OAuth client ID.
Remote and headless hosts
The callback is a temporary loopback URL such as:
http://127.0.0.1:54321/callback
When Hermes is remote, forward the exact printed port:
# Local terminal
ssh -N -L 54321:127.0.0.1:54321 user@remote-host
# Remote terminal
hermes auth add zenmux --no-browser
Use the latest login URL and port. Version 0.1.1+ waits ten minutes. For managed
containers without SSH forwarding, complete authorization in a temporary local
Hermes home and securely merge only credential_pool.zenmux into the remote
auth.json. Never paste OAuth tokens into chat or overwrite unrelated provider
credentials.
Select a model
Interactive picker:
hermes model
Direct full slug:
hermes --provider zenmux -m google/gemini-2.5-flash-lite
hermes --provider zenmux -m anthropic/claude-sonnet-4.5
Messaging command:
/model z-ai/glm-5.3-flashx
zenmux is the provider, not a model prefix. Use z-ai/glm-5.3-flashx, not
zenmux/glm-5.3-flashx.
Models absent from the catalog
The live /api/v1/models result powers the picker and typo suggestions; it is
not intended as a hard allowlist. ZenMux can accept account-, rollout-, or
route-specific slugs absent from the public catalog.
Hermes builds with ProviderProfile.model_listing_authoritative allow this
plugin to pass an unlisted slug through with a warning. Older Hermes builds
reject it before sending the request; update Hermes first. ZenMux remains the
final authority and will reject an invalid or inaccessible slug.
Configure ZenMux as the default
hermes config set model.provider zenmux
hermes config set model.default google/gemini-2.5-flash-lite
hermes config set model.base_url https://zenmux.ai/api/v1
hermes config set model.api_mode chat_completions
Verify:
hermes -z "Reply with exactly: OK" --safe-mode
Catalog behavior
The plugin reads https://zenmux.ai/api/v1/models. It:
- keeps text-output models
- filters image/video-only generation models from the chat picker
- preserves full
vendor/modelIDs - does not embed a generated catalog snapshot
- retains a small fallback list for temporary catalog failures
Update
GitHub install:
hermes plugins install ZenMux/hermes-plugin --force --enable
hermes gateway restart
PyPI install:
~/.hermes/hermes-agent/venv/bin/python -m pip install --upgrade zenmux-hermes-plugin
hermes gateway restart
Uninstall
GitHub install:
hermes auth logout zenmux
hermes plugins disable zenmux
rm -rf "${HERMES_HOME:-$HOME/.hermes}/plugins/zenmux"
PyPI install:
hermes auth logout zenmux
hermes plugins disable zenmux
~/.hermes/hermes-agent/venv/bin/python -m pip uninstall zenmux-hermes-plugin
Troubleshooting
Unknown provider 'zenmux'
hermes plugins list
hermes plugins enable zenmux
hermes gateway restart
Authorization timeout
Start a fresh login and use its new URL/port. On remote hosts, forward that port. Authorization codes from expired attempts cannot be reused.
Logged in, but inference reports no endpoint
Update the plugin and sign in again. Current credential rows include
base_url=https://zenmux.ai/api/v1; early development builds did not.
Model rejected as absent from the listing
Check the full slug first. For intentionally unlisted slugs, update Hermes to a
build supporting model_listing_authoritative, then update this plugin.
Proxy environments
Use standard HTTP_PROXY/HTTPS_PROXY. If a proxy terminates TLS, trust its CA
using SSL_CERT_FILE/REQUESTS_CA_BUNDLE. Never disable TLS verification
globally.
Development
pytest -q tests
ruff check .
python -m build
twine check dist/*
Use another registered public client only for development:
python3 configure.py zpc_YOUR_DEVELOPMENT_CLIENT_ID
Security
- HTTPS authorization/token endpoints
- callback listener bound only to
127.0.0.1 - constant-time OAuth state comparison
- S256 PKCE
- no client secret
- no token/code/state/verifier logging
- serialized refresh-token rotation through Hermes' credential lock
- token endpoint host allowlist validation
License
MIT
Release files for zenmux-hermes-plugin 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zenmux_hermes_plugin-0.1.2.tar.gz | 13.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zenmux_hermes_plugin-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.1 kB
Release files / zenmux_hermes_plugin-0.1.2.tar.gz
| Download URL | zenmux_hermes_plugin-0.1.2.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c26bc459c0541ce2e8c1144f7740d397f06426320a224af7d6065799f5411230
|
|
BLAKE2b-256 checksum How to use checksums |
35b6ec84b6eeab5978fb32408a198f2166d723750b446e9dc5ed6927f7b89900
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / zenmux_hermes_plugin-0.1.2-py3-none-any.whl
| Download URL | zenmux_hermes_plugin-0.1.2-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
43994506f28198b0058cf58899d38a005bd07e5b905523b7c3b2e29e4505c750
|
|
BLAKE2b-256 checksum How to use checksums |
1c9d3dfa39de49e27b7f97ed47e033cc07bdab275df6d9bd8cf43708b9a99eb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency log