claude-code - 💡(How to fix) Fix Claude Desktop freezes completely when Computer Use (Teach Mode / Claude in Chrome) is initiated [3 comments, 2 participants]

Error Messages/Logs

No error messages displayed — app hangs silently. No relevant entries in macOS system log (log show) for Claude process. No crash reports in ~/Library/Logs/DiagnosticReports/. Issue affects both Teach Mode and Claude in Chrome MCP flows. Freeze occurs at the point of approval/initiation, not during an active session.

TL;DR

The issue can likely be mitigated by investigating the approval dialog's interaction with the Claude Desktop app's UI thread, potentially requiring adjustments to handle asynchronous operations or permission requests.

Guidance

• Review the code handling the approval dialog and Computer Use initiation to ensure it does not block the main UI thread, causing the freeze.
• Investigate if there are any asynchronous operations or callbacks that might be interfering with the UI's responsiveness during this process.
• Consider adding logging or debugging statements to capture more detailed information about the state of the app when the freeze occurs, as the current lack of error messages or logs makes it challenging to diagnose.
• Since this is identified as a regression, comparing the code changes between the last working version (1.5354.0) and the current version might highlight the cause.

Example

No specific code example can be provided without more details on the implementation, but ensuring that UI updates and permission requests are handled on appropriate threads (e.g., using DispatchQueue.main for UI updates in Swift) is crucial.

Notes

The absence of error messages or crash reports suggests the issue might be related to how the app handles certain system interactions or permissions, rather than a straightforward coding error. The fact that it's a regression implies a recent change might be the culprit.

Recommendation

Apply workaround: Given the information, a direct fix isn't clear, but working around the issue by adjusting how the app handles the approval dialog and ensuring it doesn't block the UI thread could provide a temporary solution until the root cause is fully understood and addressed.