Unhandled promise rejection

An async failure escaped every catch and reached the process handler.

59 issues · 1 open · 58 resolved (98%) · first seen Mar 29, 2025

First response · local

What to do now

Most likely: The local Claude Code process crashed while parsing or executing.

  1. Record the Claude Code version and the first stack frame before restarting.
  2. Try a fresh session with the same minimal input to distinguish corrupted state from a repeatable crash.
  3. Preserve logs and compare reports from the same version before downgrading.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 5 new reports in the last 90 days vs 11 in the 90 before — -55%. The open backlog peaked at 9 in 2025-12 and sits at 1 today.

0 2 5 7 9 2025-032025-092026-032026-08
2025-03 — First reports2025-12 — Peak backlog (9 open)2026-01 — Most new reports (11)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

20 of these reports name the Claude Code build they were running, spanning 14 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 10 days across 58 closures. Of the 58 closures with a recorded reason, 24% were closed as completed and 44 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

15 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] Claude Desktop 1.1.4173 fails to show GUI — @formatjs/intl unhandled promise rejection crashes renderer
…ult 4. Reboot — same result 5. Directly launch — works fine Workaround Kill all processes, then launch the previous version directly: Claude Model N/A — app doesn't get far enough to connect Is this a regression? Yes, th…
Found in the description of #28271 · resolved
CLI freezes with "No messages returned" error - never recovers
…with a non-zero status code so the calling script can retry Workaround Attempted I've implemented retry logic in my bash script that: 1. Captures output to a temp file 2. Greps for "No messages returned" 3. Retries up to…
Found in the description of #19060 · resolved
[BUG] Claude Desktop 1.1.4173 crashes on startup on Windows (Squirrel install, sv-SE locale)
Confirming this also affects MSIX (Microsoft Store) installs, not just Squirrel. Detail Value -------- ------- Version 1.1.4173.0 Install method MSIX (Microsoft Store) OS Windows 1
Found in the thread of #28470 · resolved
Unhandled promise rejection in UI after successful MCP tool chain with Write + Linear update
…handling around the diff/edit acceptance UI promise chain: Workaround: Break complex tool chains into separate user prompts with 1-2 second delays between operations.
Found in the description of #10072 · resolved
[BUG] `--resume` with empty prompt (`-p ""`) causes unhandled promise rejection and zombie process
…ate (Input Validation) [reproduce-no-messages-returned.sh]( Workaround Ensure prompts are never empty when using with : Reproduction Script See attached which: 1. Creates a test session 2. Attempts to reproduce the bug 3…
Found in the description of #15918 · resolved

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–59

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. AbortError: the operation was aborted

    2,101 issues
  2. SyntaxError: Unexpected token

    698 issues
  3. Killed: 9 (SIGKILL / OOM killer)

    337 issues
  4. Segmentation fault (SIGSEGV / SIGABRT)

    289 issues
  5. TypeError: Cannot read properties of undefined

    194 issues
  6. JavaScript heap out of memory

    142 issues