I’ve been using the R1’s Hermes integration (via the rabbit-agent node) and hit one issue worth flagging. Posting here in case it helps the team and others.
When the R1 opens a Hermes session, the node spawns hermes acp and passes it a workspace cwd. The cwd it sends is /home/yt:
2026-07-23 10:13:38 [INFO] acp_adapter.session: Created ACP session <id> (cwd=/home/yt)
/home/yt doesn’t exist on my machine (my home is /home/jay). Digging into the connector binary, that path is just Rabbit’s build environment:
__dirname="/home/yt/repo/typescript/q-os3-node-agent/dist"
So the compiled connector is leaking its own build path as the agent’s working directory. Anything the Hermes session does with files or the terminal defaults to a directory that doesn’t exist, so those tools error out until you cd somewhere real.
I patched it locally in Hermes (_resolve_acp_cwd now falls back to the real home when the cwd doesn’t exist) and it works, but that patch gets wiped on the next hermes update. The real fix is on the connector side: send the host’s actual working directory (or $HOME) as the ACP cwd, not the build path.
Other than that the integration is solid. The R1’s Hermes session loads my credentials, model, memory and tools fine, and it responds well. Just the cwd is wrong.
Happy to share more logs if useful.