Persistent Hermes on Hugging Face Spaces
HermesFace packages Hermes as a Docker-based Hugging Face Space with a browser dashboard and messaging gateway, periodically syncing /opt/data to a private Dataset repository so conversations, skills, memory, and configuration survive container restarts.
Requirements
- The image passes supported Hermes environment variables through to the agent, so model providers and messaging channels can be configured with Space secrets.
- A Hugging Face account and Space with a write-capable token.
- A
HF_TOKENsecret and one model-provider key must be added to the Space. - Hugging Face account, Space, and write-capable token.
- A private Dataset repository for persistence.
- At least one supported model-provider credential.
- Optionally, a Telegram, Discord, Slack, WhatsApp, or another Hermes gateway credential.
How to use
Hugging Face quotas, sleep behavior, hardware allocations, and pricing can change, so treat free-tier and always-on claims as platform-dependent rather than permanent guarantees.
Keep the persistence Dataset private, as it may contain full conversations, memory, custom skills, and configuration.
Secrets remain server-side, but the agent still has the network and tool capabilities allowed by the Space container and Hermes configuration.
- Duplicate the public HermesFace Space.
- Create a Hugging Face token with write permission.
- Add
HF_TOKENand one model-provider key under Settings → Repository secrets. - Set
AUTO_CREATE_DATASET=true, or create a private Dataset and setHERMES_DATASET_REPOexplicitly. - Update the duplicated Space's
datasets:metadata so it does not point at the original author's dataset. - Open the Space URL and configure messaging through the dashboard or environment variables. For manual persistence, the documented settings include:
AUTO_CREATE_DATASET=true
SYNC_INTERVAL=60
TZ=UTC
HermesFace changes deployment and persistence, not Hermes's prompt model. Use the same tasks you would use locally, then restart the Space and verify that the relevant session, memory, or skill returns from the private Dataset backup.
Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.
Translation and editorial adaptation by ClawCases.
>Resources
>Related Use Cases
Agent Merge-Conflict Arbiter
Resolve a git merge conflict between two agents' branches as an impartial third party: a neutral arbiter that takes both diffs and their stated intents and produces a merged result without overwriting either side.
Automated Meeting Notes & Action Items
Turn any meeting transcript into structured notes with decisions and action items, and automatically create tasks in your project management tool.
Set up native A2A agent collaboration in Hermes
When delegating work to an A2A-compliant peer, Hermes filters inbound peer text, blocks remote slash commands, redacts credential-shaped outbound strings, rate-limits callers, and records an audit trail at ~/.hermes/a2a_audit.jsonl.