hermes - ✅(Solved) Fix [Bug]: slack gateway is reporting intermediate tool calls [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14663Fetched 2026-04-24 06:15:30
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Author
Participants
Timeline (top)
labeled ×4cross-referenced ×1referenced ×1

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

PR fix notes

PR #14746: fix(gateway): default Slack tool_progress to off

Description (problem / solution / changelog)

Summary

Slack (Bolt / Socket Mode) cannot treat tool progress like the CLI spinner: each progress line becomes a permanent channel message. The previous built-in default (new via _TIER_MEDIUM) still emitted a line on every distinct tool start, which cluttered public channels (see #14663).

This PR sets the built-in Slack default to tool_progress: "off". Other tier-2 platforms (Mattermost, Matrix, Feishu) are unchanged. Users who want progress in Slack can still enable it globally, per-platform under display.platforms.slack, or cycle with /verbose when display.tool_progress_command is true.

Changes

  • gateway/display_config.py: Slack uses {**_TIER_MEDIUM, "tool_progress": "off"} with a short comment referencing #14663.
  • tests/gateway/test_display_config.py: Split Slack from the “medium tier = new” assertion; add test_slack_defaults_tool_progress_off. Migration tests now read/write config.yaml with encoding="utf-8" so they pass on Windows default locale (GBK).
  • tests/gateway/test_verbose_command.py: /verbose isolation test expects Slack’s first cycle to go offnew instead of newall.

Testing

pytest tests/gateway/test_display_config.py tests/gateway/test_verbose_command.py -q

## Changed files

- `gateway/display_config.py` (modified, +3/-1)
- `tests/gateway/test_display_config.py` (modified, +12/-6)
- `tests/gateway/test_verbose_command.py` (modified, +3/-3)

Code Example

Report     https://paste.rs/DImlO
  agent.log  https://paste.rs/Q5VKH

---
RAW_BUFFERClick to expand / collapse

Bug Description

Tool calls are being shared in the slack chats

Debug report uploaded: Report https://paste.rs/DImlO agent.log https://paste.rs/Q5VKH

Steps to Reproduce

when running a process, the Hermes agent shares tool calls for skills and code execution

:books: skill_view: "software-development/systematic-debug..." :books: skill_view: "openclaw-imports/langsmith-trace" :snake: execute_code: "import json, glob, re, os from collec..." :snake: execute_code: "import json, glob, os records=[] for ..." (edited)

Expected Behavior

only text should be reported to the slack channel, the tool calls are meaningless

Actual Behavior

it reports tool calls

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

Slack

Debug Report

Report     https://paste.rs/DImlO
  agent.log  https://paste.rs/Q5VKH

Operating System

Ubuntu 24

Python Version

3.12.3

Hermes Version

v0.10.0 (2026.4.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

extent analysis

TL;DR

The issue can be mitigated by modifying the Hermes agent's logging configuration to exclude tool calls from being shared in Slack chats.

Guidance

  • Review the Hermes agent's configuration to identify the logging settings that control the sharing of tool calls in Slack chats.
  • Check the agent.log file (https://paste.rs/Q5VKH) for any relevant error messages or configuration settings that may be contributing to the issue.
  • Investigate the possibility of adding a filter or modifier to the logging configuration to exclude tool calls from being shared in Slack chats.
  • Consider updating the Hermes version to a newer release, if available, to see if the issue has been addressed in a later version.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The root cause of the issue is not explicitly stated, and the provided debug reports and logs may require further analysis to determine the exact cause.

Recommendation

Apply workaround: Modify the Hermes agent's logging configuration to exclude tool calls from being shared in Slack chats, as this is the most direct way to address the issue based on the provided information.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING