claude-code - 💡(How to fix) Fix [BUG] Claude Desktop (Claude Code Desktop) sessions become unresponsive ("Mustering..." forever) while other sessions work fine [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#47958Fetched 2026-04-15 06:37:27
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

No error output — the UI simply shows "Mustering..." with a spinner indefinitely. No crash, no error message. The session appears to hang before any model response is generated.

Code Example

No error output — the UI simply shows "Mustering..." with a spinner indefinitely. No crash, no error message. The session appears to hang before any model response is generated.
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?

Some sessions in Claude Desktop become permanently unresponsive. The UI shows "Mustering..." indefinitely and never produces a response.

Key observations:

  • One session (project ReflexPlusBot) works perfectly in the same app instance
  • Another session (project LookUp) is stuck — both the existing session and newly created ones for this project
  • Creating a new session for the affected project does not help
  • Restarting Claude Desktop (Cmd+Q + killall Claude) does not help
  • The issue persists across app restarts
  • Internet connection is confirmed working (other sessions respond normally)
  • No problematic hooks or MCP configurations in the affected project
  • The affected project has a standard .claude/ directory (724KB, one skill, one settings.local.json)

Environment:

  • Claude Desktop (Mac, Code mode)
  • Opus 4.6 1M model
  • Max plan
  • macOS (Apple Silicon)
  • MCP servers: sequential-thinking, context7, playwright, github, obsidian-mcp-tools
  • Bypass permissions mode enabled

What Should Happen?

Claude should answer lol

Error Messages/Logs

No error output — the UI simply shows "Mustering..." with a spinner indefinitely. No crash, no error message. The session appears to hang before any model response is generated.

Steps to Reproduce

  1. Open Claude Desktop (Code mode) on macOS
  2. Have multiple project sessions open (e.g., Project A and Project B)
  3. Project A session works normally — responds to all messages
  4. Project B session shows "Mustering..." indefinitely and never responds
  5. Create a new session for Project B — also stuck on "Mustering..."
  6. Restart Claude Desktop (Cmd+Q) — problem persists for Project B
  7. Run killall Claude in Terminal, relaunch — still stuck
  8. Project A continues to work fine in the same app instance

Note: This is NOT related to MCP servers, hooks, or project config — the affected project has a minimal .claude/ directory. The issue seems tied to a specific project/session state that survives app restarts.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.2278.0 (e5213f) 2026-04-13T17:49:21.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially resolved by investigating and resetting the project-specific state that persists across app restarts.

Guidance

  • Investigate the project directory for any files or configurations that may be causing the issue, focusing on the .claude/ directory and its contents.
  • Try deleting the .claude/ directory for the affected project (Project B) and recreate it to see if the issue resolves.
  • Check for any differences in project settings or configurations between the working project (Project A) and the affected project (Project B).
  • Consider reaching out to the development team for further assistance, as the issue seems to be related to a specific project state that survives app restarts.

Notes

The issue seems to be specific to a particular project and survives app restarts, suggesting that the problem may be related to the project's configuration or state. However, without more information about the project settings or configurations, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Try deleting the .claude/ directory for the affected project and recreate it to see if the issue resolves, as this may help reset the project-specific state that is causing the issue.

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