claude-code - 💡(How to fix) Fix [Bug] Allow prompt fails to display, UI state synchronization issue [1 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#52263Fetched 2026-04-24 06:11:49
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
0
Timeline (top)
labeled ×5subscribed ×2commented ×1unsubscribed ×1

Error Message

[{"error":"Error: Request was aborted.\n at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n at next (native:1:11)\n at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:12:27.063Z"},{"error":"Error: Request was aborted.\n at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n at next (native:1:11)\n at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:17:56.742Z"}]

Code Example

[{"error":"Error: Request was aborted.\n    at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n    at next (native:1:11)\n    at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:12:27.063Z"},{"error":"Error: Request was aborted.\n    at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n    at next (native:1:11)\n    at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:17:56.742Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description Feedback 1: Allow Prompt Not Showing Properly

I’ve noticed that in Claude CLI, the allow prompt sometimes fails to appear when it should, causing the process to stall for an extended period.

Interestingly, pressing Esc makes the prompt show up afterward.

This suggests there may be an issue with event triggering or UI state synchronization. It can easily mislead users into thinking the system is unresponsive. You may want to investigate:

Timing of allow prompt triggering UI rendering / event loop blocking Possible focus or input state issues that suppress the prompt Feedback 2: Misleading Error Message (Critical Issue)

I encountered a serious issue that should not happen in a professional tool: the system returned an error message that looked like a user rejection, even though that was not the case.

What actually happened:

After a second failure, I mistakenly retried the same job without changing strategy The correct approach would have been to switch strategies (e.g., use grep on partial content or finalize based on known XML data)

However, the more critical issue is:

I was consistently approving every prompt — I did not reject anything.

The real cause appears to be that the tool call was blocked by sandbox permission rules, but the system surfaced this as a “user rejection.”

This creates two major problems:

Incorrect attribution of failure (blaming the user instead of the system) Leads the agent to make poor decisions (e.g., unnecessary retries) Suggested Improvements Clearly distinguish error sources: User rejection Sandbox / permission denial System-level failure Provide precise and unambiguous error messages Improve observability in CLI (e.g., debug logs or error codes) Avoid mislabeling system-level failures as user actions

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.118
  • Feedback ID: 3166c096-81f3-49ae-a2b1-42d2a093cdcc

Errors

[{"error":"Error: Request was aborted.\n    at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n    at next (native:1:11)\n    at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:12:27.063Z"},{"error":"Error: Request was aborted.\n    at t86 (B:/~BUN/root/src/entrypoints/cli.js:5339:1623)\n    at next (native:1:11)\n    at dt_ (B:/~BUN/root/src/entrypoints/cli.js:8165:5609)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T05:17:56.742Z"}]

extent analysis

TL;DR

Investigate and distinguish between user rejection, sandbox permission denial, and system-level failure to provide precise error messages and improve observability in the CLI.

Guidance

  • Review the error handling mechanism to clearly differentiate between user rejection, sandbox permission denial, and system-level failures.
  • Improve error messages to provide unambiguous information about the cause of the failure.
  • Consider adding debug logs or error codes to enhance observability in the CLI.
  • Examine the event triggering and UI state synchronization to ensure the allow prompt appears as expected.

Example

No specific code snippet can be provided without modifying the existing codebase, but the error messages suggest that the cli.js file may require updates to handle errors more accurately.

Notes

The issue seems to be related to the error handling and UI rendering in the Claude CLI. The provided error messages indicate that the system is currently unable to distinguish between different types of failures, leading to misleading error messages.

Recommendation

Apply workaround: Improve error handling and messaging to clearly distinguish between user rejection, sandbox permission denial, and system-level failures, as this will help prevent incorrect attribution of failure and poor decision-making.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Allow prompt fails to display, UI state synchronization issue [1 comments, 2 participants]