v0.4.0

What's Changed

Other changes

• docs: adopt repository-first bridge contract by @m-check1B in #15
• feat: orchestration control plane + DeepSeek/Kimi ACP providers by @m-check1B in #17
• fix(deepseek): repair dsh-acp tool_call_update notifications missing toolCallId by @m-check1B in #18
• feat: Linux systemd user-service packaging by @m-check1B in #16
• fix: stop running systemd unit on uninstall when LoadState probe fails by @m-check1B in #20
• KRA-5562: public Tentacles name, doctor lab matrix by @m-check1B in #25
• Pass lab, model, and budget options through originate by @m-check1B in #21
• KRA-5639: fail closed when Hermes cannot construct openai-codex by @m-check1B in #28
• KRA-5562: publish t3-code-tentacles identity by @m-check1B in #32
• KRA-5562: make the Tentacles vertical path obvious by @m-check1B in #33
• KRA-5562: state MIT license in README by @m-check1B in #34
• KRA-5562: separate T3 native from Tentacles additions by @m-check1B in #35
• KRA-5641: fail closed on Hermes runtime provider mismatch by @m-check1B in #29
• KRA-5641: continue fail-closed Hermes threads by @m-check1B in #37
• KRA-5641: gate Hermes grok-build runtime identity by @m-check1B in #38
• KRA-5692: keep Grok Code hires out of Hermes lab by @m-check1B in #39

Full Changelog: v0.2.1...v0.4.0

v0.2.1

What's Changed

Other changes

• v0.2.1 fix: harden release pipeline by @m-check1B in #14

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

Other changes

• Harden public repository setup by @m-check1B in #4
• media: add proof-first Kimi promo v2 by @m-check1B in #8
• docs: explain why Hermes uses T3's Grok adapter by @m-check1B in #9
• docs: link the stable Hermes logo identity by @m-check1B in #10
• docs: link the public Hermes UI patch repository by @m-check1B in #11
• feat: add Pi Agent T3 harness by @m-check1B in #12
• v0.2.0 feat: rename bridge and scope Pi models by @m-check1B in #13

Full Changelog: v0.1.1...v0.2.0

Hermes for T3 Code v0.1.1

Hermes for T3 Code v0.1.1

This patch release turns the first public bridge into a safer unattended local
watcher while preserving the original three bidirectional flows.

Security boundary

• Mention routing now fails closed until the operator explicitly authorizes
  source projects and provider instances, or deliberately selects
  --allow-all-projects for a fully local deployment.
• Thread history is transferred as bounded, role-labelled untrusted context.
• Watcher state is versioned, ownership-marked, size-bounded, and validated
  before use; corrupt or foreign state is never reset into a replay risk.
• HTTP/RPC failures are redacted, and the LaunchAgent, runtime manifest, status,
  and service configuration exclude bearer values, tickets, prompts, and routed
  content.

Reliability and operations

• Retry/backoff and dead letters prevent one failing source from starving later
  healthy mentions.
• Origination accepts an idempotency key and reconciles ambiguous accepted
  responses without duplicate projects, threads, or turns.
• Existing v0.1.0 state is migrated atomically before dispatch while preserving
  links, cursors, and replay guards. A legacy file with unresolved pending
  deliveries fails closed for operator audit.
• The routing lock uses a unique owner identity and crash-safe recovery barrier.
• macOS LaunchAgents are namespaced by profile and bridge instance. Installation
  snapshots an immutable runtime, lints and verifies activation, and restores
  the prior owned service when bootstrap fails.
• service-status reports bounded private watcher health without reading or
  printing the token.

Verification

The release test suite covers routing policy,
untrusted-context bounds, replay prevention, lock recovery, retry isolation,
idempotent origination, state validation, error redaction, provider ownership,
loopback transport, token files, response limits, and namespaced service
lifecycle behavior.

Compatibility remains intentionally narrow: T3 Code 0.0.31, Hermes Agent
0.20.0, Node.js 22, and macOS. This is an independent community project and is
not affiliated with either upstream project.

Hermes for T3 Code v0.1.0

Hermes for T3 Code v0.1.0

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

This first public release connects both directions:

• use Hermes as a normal T3 Code provider over ACP;
• let Hermes or automation originate visible T3 threads;
• route new @hermes messages from any non-Hermes thread into one linked Hermes
  conversation;
• keep unrelated T3 providers untouched and make install/remove reversible.

The release includes durable replay prevention, concurrent watcher locking,
ambiguous-dispatch reconciliation, async T3 projection waits, strict provider
ownership, loopback-only authenticated transport, redirect rejection, token-file
hardening, timeouts, and payload limits.

Compatibility is deliberately narrow and honest: tested with T3 Code 0.0.31,
Hermes Agent 0.20.0, Node.js 22, and macOS. The watcher works in the foreground
where Node and both local services run; packaged background service support is
currently macOS-only.

Read the setup guide, architecture, and
build story. Real compatibility reports and focused pull
requests are welcome.