Files

T

ekko eae7195ba8 Update CLI chat session bridge (#697 )

* feat: add CLI chat sessions with Python agent bridge

Introduce a new CLI chat mode that connects Web UI directly to Hermes
Agent's AIAgent via a Python bridge subprocess and Socket.IO, bypassing
the API Server /v1/responses path. Supports streaming, slash commands
(/new, /undo, /retry, /branch, /compress, /save, /title), interrupt,
and steer.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* feat: update CLI chat session bridge

* fix: extend agent bridge startup timeouts

* docs: update bridge chat session design

* feat: align bridge compression and provider registry

* chore: bump version to 0.5.20

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-14 09:03:57 +08:00

client.ts

Update CLI chat session bridge (#697 )

2026-05-14 09:03:57 +08:00

hermes_bridge.py

Update CLI chat session bridge (#697 )

2026-05-14 09:03:57 +08:00

index.ts

Update CLI chat session bridge (#697 )

2026-05-14 09:03:57 +08:00

manager.ts

Update CLI chat session bridge (#697 )

2026-05-14 09:03:57 +08:00

README.md

Update CLI chat session bridge (#697 )

2026-05-14 09:03:57 +08:00

README.md

Agent Bridge

Optional backend-side bridge for talking to ~/.hermes/hermes-agent by instantiating run_agent.AIAgent directly in a Python process.

This is intentionally separate from the current Web UI chat path.

Python Service

python packages/server/src/services/hermes/agent-bridge/hermes_bridge.py

Default endpoint:

ipc:///tmp/hermes-agent-bridge.sock

On Windows, the default endpoint is TCP because Python may not support Unix domain sockets there:

tcp://127.0.0.1:18765

Override with:

HERMES_AGENT_BRIDGE_ENDPOINT=tcp://127.0.0.1:8765 python packages/server/src/services/hermes/agent-bridge/hermes_bridge.py

The service discovers Hermes Agent in this order:

--agent-root
HERMES_AGENT_ROOT
the installed hermes command path
current working directory and parent directories
common locations such as ~/.hermes/hermes-agent, ~/hermes-agent, and /opt/hermes-agent

Hermes home is resolved from --hermes-home, HERMES_HOME, then ~/.hermes.

Default agent root:

~/.hermes/hermes-agent

You can pass both paths explicitly:

python packages/server/src/services/hermes/agent-bridge/hermes_bridge.py \
  --agent-root ~/.hermes/hermes-agent \
  --hermes-home ~/.hermes

The socket transport uses Python and Node standard libraries. No ZMQ dependency is required.

Backend Usage

import { AgentBridgeClient } from './services/hermes/agent-bridge'

const bridge = new AgentBridgeClient()
const run = await bridge.chat(sessionId, message)

for await (const chunk of bridge.streamOutput(run.run_id)) {
  if (chunk.delta) {
    // forward chunk.delta to Socket.IO/SSE/etc.
  }
}

The external chat call only sends session_id and message. Provider, model, keys, tools, reasoning, and session DB are resolved by hermes-agent from the normal Hermes config and environment.

The bridge instantiates AIAgent with platform="cli" by default so behavior matches CLI chat. Override it only if a caller intentionally needs a distinct platform identity:

HERMES_AGENT_BRIDGE_PLATFORM=agent-bridge python packages/server/src/services/hermes/agent-bridge/hermes_bridge.py