Telegram channel: no visibility into terminal permission prompts
Resolved 💬 6 comments Opened Mar 20, 2026 by XuanLee-HEALER Closed Apr 22, 2026
Problem
When using the Telegram channel plugin to interact with Claude Code, there are two UX gaps around permission handling:
- No awareness of pending permission: When a task initiated from Telegram triggers a permission prompt in the terminal session, the Telegram user has no way to know that a permission request is pending on the terminal side. From the Telegram perspective, it just looks like Claude stopped responding.
- No feedback on rejection: If the terminal user rejects the permission, the Telegram side receives no feedback — it appears as a silent non-response with no indication of what happened.
Steps to Reproduce
- Set up the Telegram channel plugin and pair a Telegram user
- From Telegram, ask Claude Code to perform an operation that requires terminal permission (e.g., creating a directory, running a shell command)
- Observe that the Telegram user sees no indication that a permission prompt is waiting in the terminal
- Reject the permission in the terminal
- Observe that the Telegram user receives no feedback about the rejection
Expected Behavior
- The Telegram user should be notified when a task is waiting for terminal permission approval (e.g., "⏳ Waiting for terminal authorization...")
- The Telegram user should receive feedback when permission is rejected (e.g., "❌ Terminal user denied the operation")
- Consider providing a mechanism for remote channels (Telegram, etc.) to handle authorization interactions, rather than relying entirely on the terminal session
Environment
- Claude Code with Telegram channel plugin
- Permission mode: default (requires terminal approval for certain operations)
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗