Messaging toolset registration and configurability fixes

NousResearch/hermes-agent · cluster 4523 · agent

Data as of

Nothing open on GitHub. Fix merged in #10114. Check it covers your case.

The short answer

0open issues
0open PRs
11items grouped
Known?
Yes. 11 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #10114. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #10114. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple fixes addressing 'messaging' and related toolsets (honcho, send_message) being omitted from CONFIGURABLE_TOOLSETS, silently dropped from gateway/platform sessions, or excluded from tool surfaces. Also includes a Discord-specific feature and end-to-end support fix.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #10114 fix(cli): restore messaging toolset for gateway platforms

    merged to main

    files: hermes_cli/tools_config.py, tests/hermes_cli/test_tools_config.py

    Show the diff
    • hermes_cli/tools_config.py
      @@ -63,6 +63,7 @@
           ("clarify",         "❓ Clarifying Questions",      "clarify"),
           ("delegation",      "👥 Task Delegation",           "delegate_task"),
           ("cronjob",         "⏰ Cron Jobs",                 "create/list/update/pause/resume/run, with optional attached skills"),
      +    ("messaging",       "📨 Cross-Platform Messaging",  "send_message"),
           ("rl",              "🧪 RL Training",               "Tinker-Atropos training tools"),
           ("homeassistant",    "🏠 Home Assistant",           "smart home device control"),
       ]
    • tests/hermes_cli/test_tools_config.py
      @@ -8,6 +8,7 @@
           _platform_toolset_summary,
           _save_platform_tools,
           _toolset_has_keys,
      +    CONFIGURABLE_TOOLSETS,
           TOOL_CATEGORIES,
           _visible_providers,
           tools_command,
      @@ -22,6 +23,15 @@ def test_get_platform_tools_uses_default_when_platform_not_configured():
           assert enabled
       
       
      +def test_configurable_toolsets_include_messaging():
      +    assert any(ts_key == "messaging" for ts_key, _, _ in CONFIGURABLE_TOOLSETS)
      +
      +def test_get_platform_tools_default_telegram_includes_messaging():
      +    enabled = _get_platform_tools({}, "telegram")
      +
      +    assert "messaging" in enabled
      +
      +
       def test_get_platform_tools_preserves_explicit_empty_selection():
           config = {"platform_toolsets": {"cli": []}}
       

7 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 2 · closed without comment 1 · merged via another change 1 · other 1

  • #4524 fix(honcho): auto-enable honcho toolset when platform_toolsets is configured · closed without comment
  • #4553 fix(honcho): auto-enable honcho toolset when configured · superseded by another PR → #14408
  • #6007 fix(tools): add messaging to CONFIGURABLE_TOOLSETS · superseded by another PR → #10114, #8934
  • #8626 fix(cli): add messaging to configurable toolsets · done elsewhere → da8bab7
  • #8934 fix(cli): restore messaging toolset for gateway platforms · merged via another change → #10114, #6140, #6007
Show 2 more
  • #9040 fix(gateway): add messaging toolset to CONFIGURABLE_TOOLSETS · other → da8bab7, #8616
  • #15091 fix(discord): end-to-end Discord support — toolset loading, tool split, and context injection · done elsewhere
Closed issues · 3
  • Closed#4523fix(honcho): honcho toolset excluded from tool surface when platform_toolsets is configured
  • Closed#5991Tools registered to non-CONFIGURABLE_TOOLSETS keys are silently dropped from messaging-platform sessions
  • Closed#8616bug(gateway): messaging toolset missing from CONFIGURABLE_TOOLSETS — send_message silently dropped for all gateway platforms
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Merged PRs
#10114
Closed issues
3
Attempts
7 PRs closed without merging
Fix link checked
15 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.