What it is: hermes-harness-clone makes a coding harness run as your Hermes: same SOUL.md personality, same holographic fact store, same profiles and crons. You talk to it from Telegram, one topic per conversation. Google Antigravity (agy CLI) is the tested target; Claude Code and Codex adapters are in the repo but marked experimental.
Free, MIT, I'm the author.
Why: I pay for a harness subscription with big models, and my Hermes already knows everything about me. I didn't want two agents with two memories. Now whatever the clone learns goes straight into Hermes' fact store, and when it needs something only Hermes has (phone integrations, specialist profiles, plugins) it asks Hermes.
How it uses Hermes
- MCP server
hivemind (stdio, the harness starts it): core() reads USER.md/MEMORY.md, search()/about() query the fact store, conversations()/read_session() search every Hermes session across profiles, and remember() writes facts.
remember() uses the holographic provider's own store through Hermes' Python, so dedup, entities and trust behave exactly as when Hermes writes. It refuses text that looks like a secret.
ask_profile('default', ...) runs hermes -p <profile> chat -q, so the clone can hand off anything only Hermes can do.
- Crons:
crons(), create_cron() and cron_action() go through the Hermes scheduler.
- Personality: SOUL.md + USER.md are compiled into the harness instruction file (
GEMINI.md / CLAUDE.md / AGENTS.md) between markers, rebuilt every hour. Anything you wrote there by hand is kept.
PRIVATE_PROFILES: profiles listed there are invisible to every tool. I keep my wife's profile out of it.
Telegram side
- Same Threaded Mode the Hermes gateway uses: each topic maps to one harness conversation, resumed on every message.
- Commands:
/new [name], /stop, /model, /status, /soul.
- Antigravity only:
/conversations and /continue <id> move a conversation between the desktop app and Telegram.
- Owner-only (everyone else is ignored), 60 turns/hour cap by default, optional voice notes via any OpenAI-compatible Whisper endpoint.
- Optional
SENSITIVE_REGEX: matching messages go to a Hermes profile (a local model, say) and never reach the harness.
Walkthrough (real output: clean install into an empty home folder; only names redacted)
> python setup.py --harness antigravity --yes
hermes-harness-clone · harness = antigravity
[ok] antigravity binary: ...\.gemini\bin\agy.exe
[ok] HERMES_HOME: ...\.hermes
[ok] hermes binary: ...\hermes-agent\venv\Scripts\hermes.EXE
[ok] fact store memory_store.db found
[ok] python deps installed in .venv-hivemind
[ok] MCP 'hivemind' registered in antigravity
[ok] ...\.gemini\GEMINI.md updated (11905 bytes)
[ok] MCP server loads and reads Hermes memory
Ready.
> agy mcp list
NAME TYPE STATUS COMMAND/URL
hivemind stdio enabled ...\.venv-hivemind\Scripts\python.exe ...\hivemind\mcp_server.py
> agy -p "Use the hivemind MCP tool core('user') and tell me the user's first name and the name of his son."
The user's first name is [redacted], and his son's name is [redacted].
A brand-new agy home with no prior context answered from Hermes' memory on the first turn. I run the same setup on my own Telegram bot.
Install
The easy way: clone it, then tell Hermes (or Claude Code / Codex): "Read SETUP.md in this folder and set it up with the antigravity harness." SETUP.md is written for the agent: it asks you only for a Telegram bot token and your user id, runs the installer, then checks that the harness really reads your memory.
By hand:
git clone https://github.com/acruz6421-bot/hermes-harness-clone
cd hermes-harness-clone
python setup.py --harness antigravity
start_bridge.bat (./start_bridge.sh on Linux/macOS)
For topics: @BotFather → Open (the mini app, not /mybots) → your bot → Bot Settings → Threads Settings → Threaded Mode.
Limits
- Only Antigravity is tested end to end. The Claude Code and Codex adapters are written but untested; PRs welcome.
search()/remember() need the holographic memory provider. The rest works without it.
- Use a new Telegram bot: one token can only be polled by one process, so don't reuse Hermes' token.
- Turns run on your own harness subscription. agy is used unmodified through its own headless mode (
agy -p); the repo only adds an MCP server, an instruction file and the Telegram front end.
python setup.py --uninstall removes the MCP registration and the instruction block. Your Hermes memory is never touched.
Feedback welcome, especially from anyone who tries the Claude Code or Codex side.