m-check1B
Open source · MIT · v0.1.1

Idea → AI execution → reviewed release

Hermes
for T3 Code.

Put Hermes Agent in T3 Code—without forking either project.

T3 Code becomes the visible multi-agent cockpit. Hermes remains the agent runtime and orchestrator behind the scenes. A standalone bridge connects both directions and lets any T3 thread call @hermes.

View source on GitHub ↗ Download v0.1.1
01

One cockpit. Two directions.

FLOW 01

T3 → Hermes

Hermes appears as a normal T3 provider over the Agent Client Protocol.

FLOW 02

Hermes → T3

Hermes or an automation can originate a visible project, thread, and turn.

FLOW 03

Any thread → @hermes

A mention creates or continues one clearly labeled linked Hermes conversation.

02

Proof before promotion.

39/39automated tests
3live bridge flows
0upstream forks
2×independent review gates

Tested on T3 Code 0.0.31, Hermes Agent 0.20.0, Node.js 22, and macOS. The release rejects remote origins and redirects, validates its token and service ownership, locks concurrent watchers, and reconciles ambiguous dispatch by immutable IDs.

03

The product is also the receipt.

Matej described the bridge in one conversation: T3 Code as the UI, Hermes as the orchestrator, both directions connected by a separate module.

Hermes and Orbit held the goal. Codex implemented and hardened the bridge. Independent reviews rejected unsafe prototypes until bearer forwarding, replay, concurrency, projection ordering, provider collisions, and installer ownership were closed.

  1. 01Founder idea
  2. 02AI implementation
  3. 03Adversarial findings
  4. 04Corrections + canaries
  5. 05Public source

Hermes for T3 Code today

A reusable bidirectional ACP bridge tomorrow.

Try it. Break it. Bring a compatibility report. Build the next adapter.

github.com/m-check1B/t3-hermes-bridge ↗

Independent community project. Not affiliated with or endorsed by T3 Code, Ping Labs, Hermes Agent, Nous Research, or the Agent Client Protocol project.