GOBII RELEASE NOTE · HERMES COMPARISON

Gobii v2.30.0 Release Note: Observability, MCP Reliability, and Org Controls

A clearly scoped technical release note on Gobii v2.30.0, comparing shipped observability, MCP/runtime reliability, native integrations, and organization controls with Hermes Agent without conflating release claims and benchmark evidence.

Release note · July 22, 2026 · Gobii Platform · v2.30.0 release

What shipped

Gobii v2.30.0 shipped July 21, 2026 with changes spanning agent-tool parallelism, MCP authentication handling, retryable tunnel errors, shared native integration surfaces, developer-mode audit/eval/prompt archives, compact chat tables, safer exhausted-cycle closure, and organization-manager agent deletion. These are release-note claims about shipped platform behavior, not independent benchmark results.

Evidence boundary: A release note establishes what the publisher says shipped. It does not, by itself, establish comparative performance, reliability, security, or governance outcomes against Hermes Agent.

Hermes comparison matrix

Release areaComparison questionEvidence-led reading
Agent-tool parallelismHow concurrent tool work is coordinated and surfacedTreat the release note as a shipped-capability signal; validate workload-level latency and failure behavior separately.
MCP and tunnel reliabilityAuthentication handling and retryable transport errorsCompare reconnect, retry, and error-state semantics against the Hermes workflow being evaluated.
Native integrationsWhether integrations share a consistent runtime surfaceInspect permissions, setup boundaries, and failure visibility rather than assuming architectural parity.
ObservabilityAudit, evaluation, and prompt-archive support in developer modeSeparate available evidence surfaces from claims about governance outcomes; test retention and access scope.
Organization controlsExhausted-cycle closure and manager-led agent deletionReview lifecycle safety, authorization, reversibility, and audit trails before making an operations verdict.

How to evaluate the change

  1. Record the release version and date next to every comparison claim.
  2. Label shipped behavior, documented intent, and independently measured benchmark results as different evidence classes.
  3. Test the same workflow on Hermes and Gobii with equivalent permissions, tools, network conditions, and failure injection.
  4. Document where the release note is silent, especially around performance, reliability rates, and real-world governance outcomes.
  5. Update the comparison only when a material release or reproducible test changes the conclusion.

Source evidence

Gobii Platform · v2.30.0 release

Read the release in its original context. This page intentionally distinguishes documented platform changes from independent benchmark evidence and does not imply endorsement or product equivalence.