Tool calls leaking to Telegram + message flow blocking
I'm experiencing two related issues with Telegram channel:
1. Tool calls/results leaking to chat
When I make tool calls, the raw JSON (both the call and the result) is being sent to Telegram instead of being hidden. The user sees things like:
[Tool Call: gateway (ID: xxx)]
Arguments: { "action": "config.get" }
2. Message flow seems to block
After a tool call, subsequent messages don't seem to be delivered. It feels like only one message gets sent and the rest of the response is lost. The conversation "stops" mid-thought.
Environment:
• Model: google-antigravity/claude-opus-4-5-thinking (thinkingLevel: low)
• Channel: Telegram
• Clawdbot version: latest (npm installed)
Expected: Tool calls should be internal only, and all response parts should be delivered sequentially to Telegram.
Any ideas?
1. Tool calls/results leaking to chat
When I make tool calls, the raw JSON (both the call and the result) is being sent to Telegram instead of being hidden. The user sees things like:
[Tool Call: gateway (ID: xxx)]
Arguments: { "action": "config.get" }
2. Message flow seems to block
After a tool call, subsequent messages don't seem to be delivered. It feels like only one message gets sent and the rest of the response is lost. The conversation "stops" mid-thought.
Environment:
• Model: google-antigravity/claude-opus-4-5-thinking (thinkingLevel: low)
• Channel: Telegram
• Clawdbot version: latest (npm installed)
Expected: Tool calls should be internal only, and all response parts should be delivered sequentially to Telegram.
Any ideas?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
