{"slug": "connect-your-hermes-agent-directly-to-entire", "title": "Connect Your Hermes Agent Directly to Entire", "summary": "Entire published a step-by-step guide for connecting Nous Research's Hermes memory integration agent to Entire's code-linked session archive using a preview external agent adapter built from the entireio/external-agents repository. The setup requires Hermes, the Entire CLI and Go 1.26 or newer, and instructs developers to build the entire-agent-hermes executable, install it to a PATH directory, and enable external agent discovery via \"external_agents\": true in .entire/settings.json before running entire enable --agent hermes --telemetry=false. The integration attaches Hermes sessions to code so changes serve as a record of decision making, with the adapter requiring the HERMES_HOME profile variable to be set.", "body_md": "# Connect Your Hermes Agent Directly to Entire\n\nOne of the newest agents to take the developer world by storm is [Hermes](https://hermes-agent.nousresearch.com/): a memory integration agent that connects your workflows across platforms, allowing you to delegate tasks and learn from project to project. Hermes agent was developed by Nous Research, an open source applied AI research company.\n\nPart of the appeal of Hermes is its inspiration: The Greek messenger god, delivering news from realm to realm. With that in mind, Hermes agent is compatible with lots of different apps, connecting your agent sessions across the semantic and code layers. So I figured it wouldn’t be difficult to connect your Hermes sessions to Entire. And it wasn’t!\n\nTogether, Entire and Hermes give you double memory: Entire attaches your Hermes sessions to your code so that your changes are a living archive of your decision making. If you’ve started using Hermes and want to try integrating with Entire yourself, just follow these simple steps to take tasks from Hermes agents into the Entire multiverse with your team:\n\n## Ready Your Demo Environment\n\nYou’ll need Hermes and the Entire CLI installed, as well as Go 1.26 or newer to build the adapter. If you haven’t configured Hermes yet, start with the [Hermes quickstart](https://hermes-agent.nousresearch.com/docs/getting-started/quickstart) (or tell your agent to install Hermes).\n\nI used a dedicated Hermes profile for the demo to keep its configuration and sessions separate from my usual agent.\n\nIn your terminal, run:\n\n```\n$export HERMES_HOME=\"$HOME/.hermes-entire-demo\"\nhermes setup\n```\n\nComplete the model provider setup for this profile. Note that configuring your usual Hermes profile doesn’t automatically configure this one.\n\n`HERMES_HOME` tells Hermes which profile directory to use. The Entire adapter explicitly requires it, so keep that variable set for the remaining commands. You can read more about profile isolation in the [Hermes profiles docs](https://hermes-agent.nousresearch.com/docs/user-guide/profiles).\n\n## Build and Install the Adapter\n\nThe Hermes integration is currently a preview external agent adapter. Build it from the Entire external agents repo:\n\n```\n$mkdir -p \"$HOME/hermes-entire-demo\"\ncd \"$HOME/hermes-entire-demo\"\n\ngit clone https://github.com/entireio/external-agents.git\ncd external-agents/agents/entire-agent-hermes\n\ngo build -o entire-agent-hermes ./cmd/entire-agent-hermes\n```\n\nThat last command produces the `entire-agent-hermes` executable. Be sure to install it somewhere your terminal can find:\n\n```\n$mkdir -p \"$HOME/.local/bin\"\ninstall -m 755 entire-agent-hermes \\\n  \"$HOME/.local/bin/entire-agent-hermes\"\n\nexport PATH=\"$HOME/.local/bin:$PATH\"\n```\n\n`install -m 755` copies the adapter and gives it executable permissions. Entire can discover it by name if you add its directory to `PATH`.\n\nCheck that both commands resolve:\n\n```\n$command -v entire\ncommand -v entire-agent-hermes\n```\n\nThe `export` applies to this terminal session. A background Hermes gateway needs its own environment to include the adapter’s directory.\n\n## Enable Hermes in a Fresh Repository\n\nMake a separate repository for the demo:\n\n```\n$mkdir -p \"$HOME/hermes-entire-demo/demo\"\ncd \"$HOME/hermes-entire-demo/demo\"\n\ngit init\ngit commit --allow-empty -m \"Initialize Hermes demo\"\n```\n\nThe initial commit gives the demo a starting point before Hermes makes a change.\n\nConfigure Entire with:\n\n```\n$mkdir -p .entire\nprintf '{\"external_agents\":true}\\n' > .entire/settings.json\n\nentire enable --agent hermes --telemetry=false\n```\n\nHere’s what those commands do.\n\n`mkdir -p .entire` creates the directory for the repository’s Entire configuration and the `-p` flag makes it safe to run when the directory already exists.\n\n`printf` writes the setting that enables external agent discovery. Again, this example assumes a fresh repository. If you already have `.entire/settings.json`, add `\"external_agents\": true` to the existing JSON instead of replacing the file.\n\nregisters this repository with the Hermes integration. The telemetry flag disables telemetry for this setup.\n\nIf you see `Unknown agent \"hermes\"`, check adapter discovery before continuing:\n\n```\n$command -v entire-agent-hermes\ncat .entire/settings.json\necho \"$HERMES_HOME\"\nentire version\n```\n\nYou should have an executable adapter on `PATH`, external agents enabled, an explicit profile directory, and an Entire CLI version that supports the integration.\n\nIf a Hermes gateway is already running for this profile, restart it after enabling the integration:\n\n```\n$hermes gateway restart\n```\n\nThe running gateway needs to reload its plugins. Here, I’m using an interactive terminal session.\n\n## Have Hermes Make a Change\n\nFirst, print the absolute path of the file you want Hermes to create:\n\n```\n$printf '%s/video_greeting.py\\n' \"$PWD\"\n```\n\nCopy that path and then launch Hermes:\n\n```\n$hermes\n```\n\nPass it this prompt, replacing the example path with the one you just copied:\n\n```\nUse your file tools to create\n/absolute/path/to/demo/video_greeting.py.\n\nThe script should print these two lines:\nHello from Hermes!\nThis change has context.\n\nDo not commit the change.\n```\n\nThe absolute path does matter for capture because the observer uses file paths supplied to tools to associate activity with a registered repository. Running Hermes from the repository directory alone isn’t sufficient for every tool call.\n\nOnce Hermes finishes, exit and run:\n\n```\n$python3 video_greeting.py\n```\n\nYou should see:\n\n```\nHello from Hermes!\nThis change has context.\n```\n\n## Check Capture Before Committing\n\nBefore making the commit, inspect the pending capture:\n\n```\n$entire checkpoint list --pending\n```\n\nThis is the check I want before proceeding: did Entire capture the agent’s work?\n\nA pending capture doesn’t yet have a committed checkpoint ID. If you only look at the regular checkpoint list before committing, you can mistake an empty list for a broken integration.\n\nIf nothing appears under `--pending`, pause here. Confirm that Hermes used the same `HERMES_HOME` you configured, that you enabled Entire in this repository before starting the session, and that the file tool targeted an absolute path inside it.\n\n## Commit and Inspect the Checkpoint\n\nI usually have my agent handle this part (telling it to `git add` and `git commit`) but if you want to go old-school:\n\n```\n$git add video_greeting.py\ngit commit -m \"Add video greeting with Hermes\"\n```\n\nInspect the commit message:\n\n```\n$git log -1 --format=%B\n```\n\nIn my demo, it included this trailer:\n\n```\nEntire-Checkpoint: e9b55b45a8f5\n```\n\nYour checkpoint ID will be different: that trailer connects the commit to its captured agent context.\n\nNow inspect it with (or you could tell your agent to inspect it):\n\n```\n$entire checkpoint list\nentire checkpoint explain --commit HEAD\n```\n\nTo generate an AI summary, run:\n\n```\n$entire checkpoint explain --commit HEAD --generate\n```\n\nSummary generation uses Entire’s configured summary provider, so authenticate that provider first. It spends model tokens and saves the generated summary to the checkpoint.\n\nThat’s a separate step from capturing the session. A summary provider login prompt doesn’t mean the checkpoint is missing.\n\n## What the Preview Captures\n\nThe adapter captures a sanitized prompt and final response, tool names and coarse statuses, and modified file paths. It excludes Hermes memory, earlier conversation history, tool arguments, and raw tool results.\n\nThat scope matters when you inspect a checkpoint as you’re viewing the repository context retained by this integration.\n\nFor implementation details and updates as the preview evolves, see the [full Hermes and Entire setup guide](https://github.com/entireio/external-agents/tree/main/agents/entire-agent-hermes). And if you liked using Entire and Hermes together, join our [Discord](https://discord.gg/jZJs3Tue4S) to let us know!", "url": "https://wpnews.pro/news/connect-your-hermes-agent-directly-to-entire", "canonical_source": "https://entire.com/blog/connect-your-hermes-agent-directly-to-entire", "published_at": "2026-11-05 18:22:05.238004+00:00", "updated_at": "2026-11-05 18:22:07.630566+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "ai-products"], "entities": ["Entire", "Hermes", "Nous Research", "entire-agent-hermes", "entireio/external-agents", "Go 1.26", "Entire CLI"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/connect-your-hermes-agent-directly-to-entire", "markdown": "https://wpnews.pro/news/connect-your-hermes-agent-directly-to-entire.md", "text": "https://wpnews.pro/news/connect-your-hermes-agent-directly-to-entire.txt", "jsonld": "https://wpnews.pro/news/connect-your-hermes-agent-directly-to-entire.jsonld"}}