You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2026. It is now read-only.
Add config option to hide intermediate agent traces in Slack messages
Summary
When Agent Mode is enabled, the Slack bot posts intermediate reasoning/tool traces such as Thought, Justification, Action, and Action Input directly into the user thread. This is noisy for end users and exposes internal planner format that should stay internal.
Problem
For production support and business workflows, we only want the final user-facing outcome in Slack.
Current behavior posts multiple intermediate messages before the final answer.
Observed behavior
Bot posts lines like:
Thought: Do I need to use a tool? Yes
Justification: ...
Action: ...
Action Input: ...
These appear as separate Slack messages in the conversation thread.
Expected behavior
By default or via configuration, bot should optionally suppress intermediate agent traces.
Only final synthesized, user-friendly response should be posted to Slack.
Why this matters
Better user experience in Slack
Avoid exposing internal prompt/planner structure
Reduces message noise and confusion
Safer for non-technical users
Proposed change
Add a new config flag in the unified config schema, for example:
Path: llm.suppressIntermediateSteps
Type: boolean
Default: false (to preserve current behavior)
Behavior
false: keep current behavior
true: do not send intermediate Thought/Action messages to Slack, only final response
Implementation idea
In the agent callback flow, filter intermediate outputs before calling sendMessage, or only emit on final chain completion event intended for end-user output.
Acceptance criteria
With useAgent: true and suppressIntermediateSteps: true:
No Thought / Action / Action Input messages are posted to Slack
Final answer is still posted correctly
With suppressIntermediateSteps: false:
Existing behavior remains unchanged
Config schema and docs are updated with this option
Add config option to hide intermediate agent traces in Slack messages
Summary
When Agent Mode is enabled, the Slack bot posts intermediate reasoning/tool traces such as
Thought,Justification,Action, andAction Inputdirectly into the user thread. This is noisy for end users and exposes internal planner format that should stay internal.Problem
For production support and business workflows, we only want the final user-facing outcome in Slack.
Current behavior posts multiple intermediate messages before the final answer.
Observed behavior
Thought: Do I need to use a tool? YesJustification: ...Action: ...Action Input: ...Expected behavior
Why this matters
Proposed change
Add a new config flag in the unified config schema, for example:
llm.suppressIntermediateStepsbooleanfalse(to preserve current behavior)Behavior
false: keep current behaviortrue: do not send intermediateThought/Actionmessages to Slack, only final responseImplementation idea
In the agent callback flow, filter intermediate outputs before calling
sendMessage, or only emit on final chain completion event intended for end-user output.Acceptance criteria
useAgent: trueandsuppressIntermediateSteps: true:Thought/Action/Action Inputmessages are posted to SlacksuppressIntermediateSteps: false:Environment
slack-mcp-clientlatest release