Gobii v2.28.0 — Template Editor, Teams Section, and Admin Directives Deepen the Platform Gap
Released July 2 at 22:29 UTC, barely 24 hours after v2.27.0. Template editing, a Teams data model, admin directives flowing through unified history, and a disciplined 40% code-quality allocation. The shipping cadence alone is a meaningful Hermes-vs-Gobii comparison signal.
Main Signal
Gobii v2.28.0 introduces a Template Editor for org admins, a new Teams section, admin system directives routed through unified history, and roughly 40% code-quality/debt-reduction PRs. This release lands one day after v2.27.0 (which shipped streaming, bulk outreach, and TTFT observability). The combined v2.27-v2.28 velocity tells a story about managed-runtime development pace that contrasts sharply with Hermes Agent's current public signal set, which remains weighted toward operational reliability and packaging bugs.
Release Breakdown
| Area | Signal | Comparison Implication |
|---|---|---|
| Template Editor (#1223) | Org admins can create and edit agent templates via the UI — the write-side of the template system introduced in v2.26.0. | Templates plus one-click provisioning (#1220) suggest an agent-provisioning pipeline: define a template once, then instantiate agents with a dropdown. Hermes has no equivalent organizational template primitive. |
| Teams Section (#1215) | A new Teams section in the UI — the data model is expanding: agents → templates → teams. | Teams as a first-class abstraction (group of agents? shared context? RBAC boundary?) indicates organizational multi-agent design. Hermes' current public architecture does not expose a comparable team primitive. |
| Admin System Directives (#1228) | Admin messages now flow through the unified history system rather than a separate channel. | Unified history is becoming the communication backbone. Directives as a message type in the history schema is an architectural decision that affects auditability, replay, and cross-agent consistency. |
| Chat Infrastructure (#1230) | Refined agent chat delivery, timeline, and notification handling. | Chat polish signals investment in the core user interaction surface while Hermes' public issues include TUI packaging failures and gateway startup problems. |
Code-Quality Discipline (40% of the Release)
| PR | Type | What It Signals |
|---|---|---|
| #1227 | UI bug fixes and improvements | Continuous polish, not deferred to a cleanup sprint |
| #1224 | Remove unused frontend endpoint data from console APIs | API surface hygiene — shrinking attack/confusion surface |
| #1221 | Remove unneeded feature flags and simplify shell rendering | Feature-flag lifecycle discipline — flags are removed, not left to accumulate |
| #1229 | Remove obsolete console diagnostics screen | Dead code elimination — reduces maintenance burden |
| #1222 | Update homepage sourcing hero copy | Content iteration alongside engineering |
The pattern is worth noting: nearly half the release is cleanup. That is not a sign of accumulated mess — it is a sign of a team that removes feature flags, dead endpoints, and obsolete screens in the same release cycle that adds new capabilities. For a managed runtime, that discipline reduces the long-term bug surface that Hermes Agent currently struggles with on the packaging, persistence, and startup fronts.
Shipping Velocity as a Comparison Signal
| Dimension | Gobii (v2.27 → v2.28) | Hermes Agent (Current Public Signal) |
|---|---|---|
| Release cadence | Two releases in ~24 hours (July 1 and July 2) | Hermes v0.18.0 (2026.7.1) shipped with a re-regressed TUI packaging bug (#57031) |
| Feature surface | Streaming API, bulk outreach, interactive worker, TTFT, template editor, teams, admin directives | Public issue flow dominated by packaging, memory persistence, gateway startup, and sandbox isolation failures |
| Code-quality balance | ~40% cleanup PRs per release — feature flags removed, dead endpoints deleted, API surface shrunk | Bug tracker shows re-regressions (#19514 → #57031), unremoved stale state files (#56396), and isolation bugs (#57045, #54354) |
| Architectural evolution | Data model expanding: agents → templates → teams; unified history absorbing directives | Architectural discussion still weighted toward local runtime fragility rather than organizational primitives |
Honest Comparison Note
Gobii and Hermes Agent serve different deployment philosophies: managed platform vs local-first agent. But the comparison that matters to users is practical, not philosophical. When one system ships streaming, observability, template provisioning, team abstractions, and admin directives in a 24-hour window while the other is still absorbing TUI packaging regressions and sandbox-isolation data-loss bugs, the runtime gap is not theoretical. It is visible in the release notes and the bug tracker side by side.
Context from Recent Hermes Agent Bug Pages
Comparison signal page published by hermes-agent.reviews — July 3, 2026
https://hermes-agent.reviews/gobii-v228-template-editor-teams.html