claude-code - 💡(How to fix) Fix Channel notifications dropped after idle — messages lost between turns [1 comments, 2 participants]

• First message after session start: delivered ✅
• Subsequent messages after a completed turn: ~70% dropped silently
• Sometimes 3-4 messages need to be sent before one gets through
• Adding a Stop hook that sends a status message to Telegram confirms the session is idle, but next message is still dropped
• No error in stderr, no 409 conflict — message simply never arrives

TL;DR

Investigate and potentially update the telegram@claude-plugins-official plugin to address the message dropping issue, considering the plugin's long polling configuration and compatibility with supergroups having forum topics enabled.

Guidance

• Review the telegram@claude-plugins-official plugin's documentation and configuration options to ensure proper setup for handling messages in supergroups with forum topics, especially focusing on any settings related to long polling and message handling.
• Check for any updates to the telegram@claude-plugins-official plugin, as the issue might have been addressed in a newer version, considering the current version used is v0.0.4.
• Inspect the Claude Code and plugin logs for any subtle errors or warnings that might indicate why messages are being dropped, even if no error is visible in stderr.
• Consider testing the setup with a different channel or configuration to isolate if the issue is specific to supergroups with forum topics or a more general problem.

Example

No specific code snippet can be provided without more details on the plugin's API and the exact configuration used. However, ensuring that the plugin is properly configured for the specific use case (supergroups with forum topics) is crucial.

Notes

The issue seems to be related to the interaction between Claude Code, the telegram@claude-plugins-official plugin, and the specific setup of the Telegram group. The fact that similar issues have been reported (#40604, #38259, #36477) suggests a potential pattern or known problem that might be addressed by updating the plugin or adjusting the configuration.

Recommendation

Apply workaround: Given the nature of the issue and the lack of a clear solution, applying a workaround such as frequently sending "keep-alive" messages or adjusting the plugin's configuration to better handle long polling in supergroups might mitigate the problem until a more permanent fix is available.