Description
When the agent makes tool calls (exec, read, etc.), the internal progress/working status messages are being exposed to Telegram chats as visible messages. Users see things like:
Working... • exec show...
Working... • exec ls ~/Desktop
Working... • read /path/to/file
These should be hidden internal processing indicators, not user-facing messages.
Environment
- OpenClaw version: 2026.4.22 and 2026.4.23 (both affected)
- Channel: Telegram (direct messages and groups)
- Model: Tested with Claude Sonnet 4.6, Claude Opus 4.6, Gemini 2.5 Flash
- OS: macOS (Darwin 25.2.0 arm64)
Steps to Reproduce
- Connect OpenClaw to Telegram
- Send a message that triggers tool use (e.g., ask the agent to check a file)
- Observe Telegram chat — internal tool call progress messages appear as visible messages
Expected Behavior
Tool call progress should not be visible to the user in Telegram. Only the final assistant response should be sent.
Actual Behavior
Every tool call shows a "Working... • [tool name] [partial args]" message in the Telegram chat before the actual response.
Notes
- Started occurring around 9 AM ET on April 24, 2026
- Affects all Telegram groups and DMs connected to the bot
- Gateway restart does not fix it
- May be related to model switching (multiple model changes were made around the time it started)
- This is very disruptive in group chats where non-admin users can see the internal processing
Description
When the agent makes tool calls (exec, read, etc.), the internal progress/working status messages are being exposed to Telegram chats as visible messages. Users see things like:
These should be hidden internal processing indicators, not user-facing messages.
Environment
Steps to Reproduce
Expected Behavior
Tool call progress should not be visible to the user in Telegram. Only the final assistant response should be sent.
Actual Behavior
Every tool call shows a "Working... • [tool name] [partial args]" message in the Telegram chat before the actual response.
Notes