GOBII RELEASE NOTE · COMPARISON FRAMEWORK
Gobii v2.30.1: Runtime State, Scheduling, Webhooks, and Shared-Channel Governance
A release-note-grounded framework for assessing shipped Gobii platform changes alongside Hermes Agent operating concerns, without converting feature notes into unsupported performance or reliability claims.
What shipped
The linked v2.30.1 release lists work on a maintained SQLite domain model, incremental and reliable SQLite transactions, bounded multi-schedules, webhook tools, Meta Gobii and MCP event handling, charter and state synchronization, persistent chat preferences, and role-boundary and shared-channel behavior.
Evidence boundary: These are release-note claims about shipped changes. They are not independent benchmarks, a product-wide reliability estimate, or proof that Gobii outperforms Hermes Agent in a particular environment.
Technical comparison lens
| Release signal | What the release says | Evidence-led comparison question |
|---|---|---|
| Runtime state model | Maintained SQLite domain-model and incremental transaction work are listed in the release. | For a managed-agent comparison, evaluate whether state, provenance, and recovery behavior are observable in the actual deployment. Do not infer a benchmark advantage from release notes alone. |
| Scheduling surface | Bounded multi-schedule behavior is listed in the release. | Compare scheduling limits, timezone handling, cancellation behavior, and delivery semantics using documented configurations or a disclosed test protocol. |
| Webhook and event handling | Webhook tools plus Meta Gobii and MCP event-handling fixes are listed. | Separate shipped integration capability from reliability claims. Test the exact trigger, payload, authorization, and failure path before drawing conclusions. |
| Charter and preference state | Charter/state synchronization and persistent chat preferences are listed. | Assess whether durable guidance survives the relevant lifecycle events without silently overriding current user intent. |
| Shared-channel governance | Role-boundary and shared-channel behavior are listed. | Evaluate permission boundaries, recipient context, escalation, and whether an agent avoids acting on instructions outside its authorized scope. |
Evaluation protocol before a verdict
- Pin the product versions, deployment mode, configuration, permissions, and test date.
- Define a workflow with observable state transitions, expected delivery behavior, and a safe failure path.
- Record raw outcomes for success, partial completion, cancellation, duplicate delivery, and unknown remote state.
- Evaluate shared-channel behavior with explicit recipient context and role-boundary cases.
- Publish limitations, excluded integrations, and any evidence that conflicts with the conclusion.
Source evidence
Gobii Platform v2.30.1 release
Consult the original release notes for the complete change list and later corrections. Any Hermes comparison should be based on like-for-like, dated evidence and should keep release claims separate from measured outcomes.