Activity

Commit pace

95 commits

22 contributors

54 PRs merged

0 releases

25 issues closed

95 so far · 140 median over prior 13 days
  1. Monday, July 13: 109 first-parent commits
  2. Tuesday, July 14: 81 first-parent commits
  3. Wednesday, July 15: 134 first-parent commits
  4. Thursday, July 16: 240 first-parent commits
  5. Friday, July 17: 140 first-parent commits
  6. Saturday, July 18: 140 first-parent commits
  7. Sunday, July 19: 82 first-parent commits
  8. Monday, July 20: 184 first-parent commits
  9. Tuesday, July 21: 118 first-parent commits
  10. Wednesday, July 22: 272 first-parent commits
  11. Thursday, July 23: 368 first-parent commits
  12. Friday, July 24: 215 first-parent commits
  13. Saturday, July 25: 93 first-parent commits
  14. Sunday, July 26: 95 first-parent commits so far
Top contributors
  1. teknium143
  2. brooklyn!22
  3. hermes-seaeye[bot]6
Focus areas
  1. Tests51
  2. Hermes Cli28
  3. Apps / Desktop25
Integrations / plugins
  1. Discord2
  2. Telegram2
  3. Feishu1

Summary

July 26 bounds tool context, lengthens agent runs, and hardens runtime continuity.

Tiered tool disclosure remains the day's main architectural move, keeping catalogs of 830 schemas usable within an explicit budget. The default tool-calling limit rose from 90 to 500, while late updater and gateway fixes preserve service and session continuity around longer runs. Guarded recovery remains the safety model for the deeper work these changes enable.

Read on their thinking

Tool discovery is being treated as an information-budget problem rather than a larger prompt. Progressive disclosure, catalog summaries, and adversarial benchmarks now form one tested design.

Recovery continues to require positive safety evidence. Partial salvage is opt-in, live databases cannot be snapshotted, and reconstructed sessions are retained rather than discarded.

Hermes is increasing the permitted depth of tool-driven work while tightening runtime continuity around it. The higher iteration ceiling is now paired with tested updater restarts and notification scoping.

What changed

Compared with 2026-07-25, 2026-07-26 has 95 commits versus 93, 22 contributors versus 30, and 54 merged pull requests versus 60. It also has 0 published releases versus 0 and 25 closed issues versus 38.

What shipped

Tool disclosure now scales with catalog size0986ac393MCP and plugin tools are deferred into tiered discovery, with focused tests and documentation defining the listing behavior.The default tool-calling limit rose from 90 to 5001b081e489The higher default applies across agent initialization, CLI configuration, scheduling, gateway entry points, tests, and documentation.Updates no longer blindly reinstall cua-driver920facdc4The update path now preserves an existing driver installation while tests cover the guarded behavior.

What they are prioritizing

  1. 01

    Keep large tool catalogs discoverable within explicit listing budgets.

  2. 02

    Preserve recovered session data without reading or snapshotting unsafe live state.

  3. 03

    Preserve service and session identity through updates and asynchronous notification delivery.

Continuous threads

Bounded tool discovery

Established at production-scale catalogs

Tiered disclosure defers MCP and plugin schemas while preserving full catalog access through search and explicit listing.

Failure containment

Strengthened from safe inspection into guarded salvage

Recovery refuses live snapshots, reports damaged metadata as loss, and reconstructs missing sessions without deleting salvaged messages.

Runtime continuity

Extending from scoped delivery into update recovery

Kanban wake-ups preserve chat type and creator session keys, while updater restarts restore supervised or manually started backends.

New signals

Observed

Commits e869accc1, 0986ac393, and e9fe060eb implement catalog listings, tiered disclosure, and a 5% default listing budget.

Observed

Commit 1b081e489 raises the default tool-calling iteration limit from 90 to 500 across runtime entry points, configuration, tests, and documentation.

Observed

Commits a417c6e08 and 2a2ae3bca preserve kanban chat type and verify that a DM wake resumes the creator's real DM session key.

Observed

Commits 13590ce68 and 83bba799e extend MEDIA handling to spaced paths, GIS extensions, safe display stripping, and history-aware deduplication.

Observed

Commits d1f376006 and 8e1fb9ea3 restore stale backends after updates under supervised and manual launch modes.

Inference

Hermes is pairing a larger execution horizon with stricter context limits and more explicit runtime restoration.

Covers every calendar day from through 2026-07-26, based on first-parent commit history through 920facdc4, release notes, public issues, pull requests, and repository architecture. Observations are factual; inferences are editorial readings, not maintainer statements. Activity counts use mainline commit authors and GitHub merge, release, and issue-close timestamps; focus areas use explicit commit scopes, while integration signals require changes inside declared plugin, platform, or MCP namespaces.