Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Telegram permission reply after local fallback timeout is silently dropped — allowlist not updated

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Root cause (suspected): After the 60s timeout, the Telegram handler stops listening for replies on that message. Late-arriving replies have no consumer and are dropped without any error or notification.

Error Messages/Logs

Root Cause

Root cause (suspected): After the 60s timeout, the Telegram handler stops listening for replies on that message. Late-arriving replies have no consumer and are dropped without any error or notification.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Description:

When a permission request is sent to Telegram and the user doesn't reply within the 60-second timeout, the system correctly falls back to the local IDE confirmation dialog. However, if the user then replies to the Telegram message (e.g. okkk to add to global allowlist) after the timeout has already occurred, the reply is silently discarded — the allowlist is never updated and no feedback is given to the user.

Steps to reproduce:

A permission prompt is sent to Telegram Do not reply within 60 seconds — local IDE dialog appears After the IDE dialog appears, reply okkk in Telegram Approve the action in the local IDE dialog Expected behavior: Either (a) the late Telegram reply is still processed to update the allowlist, or (b) the user receives a feedback message in Telegram indicating the reply arrived too late and the allowlist was not updated.

Actual behavior: The okkk reply is silently ignored. The action is allowed once via the local IDE dialog, but the global allowlist is not updated. The user has no indication that their allowlist intent was not applied.

Root cause (suspected): After the 60s timeout, the Telegram handler stops listening for replies on that message. Late-arriving replies have no consumer and are dropped without any error or notification.

What Should Happen?

Either (a) the late Telegram reply is still processed to update the allowlist, or (b) the user receives a feedback message in Telegram indicating the reply arrived too late and the allowlist was not updated.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

A permission prompt is sent to Telegram Do not reply within 60 seconds — local IDE dialog appears After the IDE dialog appears, reply okkk in Telegram Approve the action in the local IDE dialog

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.131 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING