Summary

Title: Telegram channel stops sending messages after receiving an image

Description

There is a critical issue with the Telegram channel provider where it stops sending messages from the agent to the user. The agent continues to receive messages from Telegram, but all outbound messages fail silently.

Steps to Reproduce

The issue appears to be related to session state and is reliably triggered by receiving an image file.

1. Start a conversation with the OpenClaw agent via Telegram.
2. If the connection is broken, clearing the chat history in Telegram and sending /start temporarily fixes it.
3. Text-based messages are exchanged successfully in both directions.
4. The user sends an image (e.g., a screenshot) to the agent.
5. The agent receives the image successfully.
6. From this point on, all subsequent outbound messages from the agent fail to be delivered to Telegram. The agent continues to receive inbound text messages.

Troubleshooting Steps Performed

We have performed extensive troubleshooting and have ruled out common configuration and network issues:

1. Gateway Restart: openclaw gateway restart was performed multiple times. It temporarily fixed the connection once (after a /start from the user) but did not solve the underlying issue.
2. New Bot Token: We generated a new bot token via BotFather, updated it in openclaw.json, and restarted the gateway. The issue persisted.
3. Network Connectivity Test: We performed a direct curl call to the Telegram API from the server, which was successful. This confirms there are no firewall, DNS, or network-level blocks.
   • Command: curl https://api.telegram.org/bot<REDACTED_TOKEN>/getMe
   • Result: {"ok":true,"result":{"id":8613918585,"is_bot":true,"first_name":"Glitch","username":"glitch_gs_bot",...}}
4. Configuration Review: We reviewed the documentation for session, memory, compaction, and pruning. The agent's configuration uses standard defaults and no misconfigurations were found that could cause this issue.

Conclusion

The issue is not related to network connectivity, API token validity, or user configuration. All evidence points to an internal bug in the OpenClaw Telegram channel provider that causes its outbound message queue to fail after processing an inbound media file (image).

Steps to reproduce

Title: Telegram channel stops sending messages after receiving an image

Description

There is a critical issue with the Telegram channel provider where it stops sending messages from the agent to the user. The agent continues to receive messages from Telegram, but all outbound messages fail silently.

Steps to Reproduce

The issue appears to be related to session state and is reliably triggered by receiving an image file.

1. Start a conversation with the OpenClaw agent via Telegram.
2. If the connection is broken, clearing the chat history in Telegram and sending /start temporarily fixes it.
3. Text-based messages are exchanged successfully in both directions.
4. The user sends an image (e.g., a screenshot) to the agent.
5. The agent receives the image successfully.
6. From this point on, all subsequent outbound messages from the agent fail to be delivered to Telegram. The agent continues to receive inbound text messages.

Troubleshooting Steps Performed

We have performed extensive troubleshooting and have ruled out common configuration and network issues:

1. Gateway Restart: openclaw gateway restart was performed multiple times. It temporarily fixed the connection once (after a /start from the user) but did not solve the underlying issue.
2. New Bot Token: We generated a new bot token via BotFather, updated it in openclaw.json, and restarted the gateway. The issue persisted.
3. Network Connectivity Test: We performed a direct curl call to the Telegram API from the server, which was successful. This confirms there are no firewall, DNS, or network-level blocks.
   • Command: curl https://api.telegram.org/bot<REDACTED_TOKEN>/getMe
   • Result: {"ok":true,"result":{"id":8613918585,"is_bot":true,"first_name":"Glitch","username":"glitch_gs_bot",...}}
4. Configuration Review: We reviewed the documentation for session, memory, compaction, and pruning. The agent's configuration uses standard defaults and no misconfigurations were found that could cause this issue.

Conclusion

The issue is not related to network connectivity, API token validity, or user configuration. All evidence points to an internal bug in the OpenClaw Telegram channel provider that causes its outbound message queue to fail after processing an inbound media file (image).

Expected behavior

Title: Telegram channel stops sending messages after receiving an image

Description

There is a critical issue with the Telegram channel provider where it stops sending messages from the agent to the user. The agent continues to receive messages from Telegram, but all outbound messages fail silently.

Steps to Reproduce

The issue appears to be related to session state and is reliably triggered by receiving an image file.

1. Start a conversation with the OpenClaw agent via Telegram.
2. If the connection is broken, clearing the chat history in Telegram and sending /start temporarily fixes it.
3. Text-based messages are exchanged successfully in both directions.
4. The user sends an image (e.g., a screenshot) to the agent.
5. The agent receives the image successfully.
6. From this point on, all subsequent outbound messages from the agent fail to be delivered to Telegram. The agent continues to receive inbound text messages.

Troubleshooting Steps Performed

We have performed extensive troubleshooting and have ruled out common configuration and network issues:

1. Gateway Restart: openclaw gateway restart was performed multiple times. It temporarily fixed the connection once (after a /start from the user) but did not solve the underlying issue.
2. New Bot Token: We generated a new bot token via BotFather, updated it in openclaw.json, and restarted the gateway. The issue persisted.
3. Network Connectivity Test: We performed a direct curl call to the Telegram API from the server, which was successful. This confirms there are no firewall, DNS, or network-level blocks.
   • Command: curl https://api.telegram.org/bot<REDACTED_TOKEN>/getMe
   • Result: {"ok":true,"result":{"id":8613918585,"is_bot":true,"first_name":"Glitch","username":"glitch_gs_bot",...}}
4. Configuration Review: We reviewed the documentation for session, memory, compaction, and pruning. The agent's configuration uses standard defaults and no misconfigurations were found that could cause this issue.

Conclusion

The issue is not related to network connectivity, API token validity, or user configuration. All evidence points to an internal bug in the OpenClaw Telegram channel provider that causes its outbound message queue to fail after processing an inbound media file (image).

Actual behavior

Title: Telegram channel stops sending messages after receiving an image

Description

There is a critical issue with the Telegram channel provider where it stops sending messages from the agent to the user. The agent continues to receive messages from Telegram, but all outbound messages fail silently.

Steps to Reproduce

The issue appears to be related to session state and is reliably triggered by receiving an image file.

1. Start a conversation with the OpenClaw agent via Telegram.
2. If the connection is broken, clearing the chat history in Telegram and sending /start temporarily fixes it.
3. Text-based messages are exchanged successfully in both directions.
4. The user sends an image (e.g., a screenshot) to the agent.
5. The agent receives the image successfully.
6. From this point on, all subsequent outbound messages from the agent fail to be delivered to Telegram. The agent continues to receive inbound text messages.

Troubleshooting Steps Performed

We have performed extensive troubleshooting and have ruled out common configuration and network issues:

1. Gateway Restart: openclaw gateway restart was performed multiple times. It temporarily fixed the connection once (after a /start from the user) but did not solve the underlying issue.
2. New Bot Token: We generated a new bot token via BotFather, updated it in openclaw.json, and restarted the gateway. The issue persisted.
3. Network Connectivity Test: We performed a direct curl call to the Telegram API from the server, which was successful. This confirms there are no firewall, DNS, or network-level blocks.
   • Command: curl https://api.telegram.org/bot<REDACTED_TOKEN>/getMe
   • Result: {"ok":true,"result":{"id":8613918585,"is_bot":true,"first_name":"Glitch","username":"glitch_gs_bot",...}}
4. Configuration Review: We reviewed the documentation for session, memory, compaction, and pruning. The agent's configuration uses standard defaults and no misconfigurations were found that could cause this issue.

Conclusion

The issue is not related to network connectivity, API token validity, or user configuration. All evidence points to an internal bug in the OpenClaw Telegram channel provider that causes its outbound message queue to fail after processing an inbound media file (image).

OpenClaw version

Version 2026.2.26

Operating system

macOS Tahoe 26.1

Install method

VPS

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response