[BUG]
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Summary
After upgrading to Claude 1.6608.2 (ebf1a1), I encountered an issue using Claude Code in the macOS app. Claude appeared to become stuck while performing a task. From my end, there was no useful progress update, error message, or communication that the task had stalled. During this time, it appeared to continue consuming a significant amount of my session limit.
The console showed repeated errors and warning spam, including:
- repeated GitHub authentication errors
- repeated preload warnings for font and CSS assets
- ProseMirror CSS warnings
- Intercom / Google Analytics warning spam
- a possible EventEmitter memory leak warning
The main user-facing issue is that Claude appeared to be working or stalled without communicating anything while session usage continued to be consumed.
Environment
- App: Claude macOS app
- Version: Claude 1.6608.2 (ebf1a1)
- Feature: Claude Code
- Date observed: 2026-05-12
- Platform: macOS
- Public report note: organization IDs and static asset URLs are redacted below
What Should Happen?
Expected behavior
If Claude Code gets stuck, blocked, or encounters an internal, tool, or authentication issue during a task:
- Claude should clearly tell the user that something went wrong or that it cannot continue.
- Claude should stop the task rather than silently continuing.
- Claude should not continue consuming a significant amount of the user’s session limit while making no visible progress.
- If an integration such as GitHub requires authentication, the UI should ask the user to authenticate or skip that integration.
- Repeated background errors should be handled gracefully and should not cause the user-facing task to hang.
Actual behavior
Claude Code appeared to become stuck while working on a task in the macOS app after upgrading to Claude 1.6608.2 (ebf1a1).
From my end:
- There was no useful progress update.
- There was no clear error message.
- The task appeared to continue running or remain stuck.
- It appeared to consume a significant amount of my session limit while making no visible progress.
- The console showed repeated errors and warnings during the same period.
Impact
- Claude Code appeared stuck while performing a task.
- No useful progress or failure message was shown to the user.
- A significant amount of my session limit appeared to be consumed while no visible progress was made.
- Console output was heavily polluted with repeated warnings and errors.
- Repeated
401 auth_requirederrors suggest the app may be repeatedly trying to access a GitHub-related endpoint even when GitHub authentication is missing.
- The repeated errors/warnings made it harder to tell what actually caused the stall.
- This started after upgrading to Claude 1.6608.2 (ebf1a1).
Why this seems problematic
A missing GitHub authentication state should not cause Claude Code or the task UI to hang silently. If GitHub authentication is required, the app should either prompt the user to authenticate, skip the GitHub-dependent step, or fail gracefully with a visible message.
Also, if a task is blocked internally, the app should not continue consuming the user’s limited session quota without making visible progress.
Error Messages/Logs
## Minimal public-safe log excerpt
[warn] MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ... AutoUpdater ... listeners added. Use emitter.setMaxListeners() to increase limit
[error] [REACT_QUERY_CLIENT] QueryClient error:
{
"type": "authentication_error",
"statusCode": 401,
"details": {
"type": "github",
"error_visibility": "user_facing",
"error_code": "auth_required"
},
"errorCode": "auth_required",
"endpoint": "/api/organizations/<ORG_ID>/code/repos?skip_status=true",
"method": "GET",
"message": "You must authenticate with GitHub."
}
[warn] ProseMirror expects the CSS white-space property to be set, preferably to 'pre-wrap'.
[warn] Intercom - Google Analytics is not installed or configured, have you forgotten to include it?
[warn] The resource <STATIC_ASSET_URL> was preloaded using link preload but not used within a few seconds from the window's load event.
### Repeated GitHub authentication error
The console repeatedly logged a React Query client error indicating that GitHub authentication was required:
[REACT_QUERY_CLIENT] QueryClient error:
{
"type": "authentication_error",
"statusCode": 401,
"details": {
"type": "github",
"error_visibility": "user_facing",
"error_code": "auth_required"
},
"errorCode": "auth_required",
"endpoint": "/api/organizations/<ORG_ID>/code/repos?skip_status=true",
"method": "GET",
"message": "You must authenticate with GitHub."
}
This error appeared multiple times during the session.
### Possible EventEmitter memory leak warning
The console showed the following warning:
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ... AutoUpdater ... listeners added. Use emitter.setMaxListeners() to increase limit
This may indicate that listeners are being repeatedly attached without cleanup, although I cannot confirm whether it is related to the user-facing stall.
### ProseMirror CSS warning
The console showed the following ProseMirror warning:
ProseMirror expects the CSS white-space property to be set, preferably to 'pre-wrap'. It is recommended to load style/prosemirror.css from the prosemirror-view package.
This warning appeared more than once.
### Intercom / Google Analytics warning spam
The console repeatedly showed the following warning:
Intercom - Google Analytics is not installed or configured, have you forgotten to include it?
This warning appeared many times in a short period.
### Preload warnings
The console repeatedly showed warnings like:
The resource <STATIC_ASSET_URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
These included multiple font and CSS assets. Exact asset URLs are redacted because they do not seem necessary for a public report.
Examples of redacted asset types:
/_next/static/media/<HASH>.woff2
/_next/static/css/<HASH>.css
Steps to Reproduce
Steps to reproduce
- Install or upgrade to Claude 1.6608.2 (ebf1a1) on macOS.
- Open the Claude macOS app.
- Start a Claude Code task.
- Use Claude Code in a context where GitHub authentication is not currently available, expired, disconnected, or not completed.
- Ask Claude Code to perform a task that may involve accessing or listing code repositories.
- Observe that Claude Code appears to continue working without providing a useful progress update, completion, or visible failure message.
- Open the app’s developer console / logs.
- Observe repeated console errors similar to:
``text``
[REACT_QUERY_CLIENT] QueryClient error:
{
"type": "authentication_error",
"statusCode": 401,
"details": {
"type": "github",
"error_visibility": "user_facing",
"error_code": "auth_required"
},
"errorCode": "auth_required",
"endpoint": "/api/organizations/<ORG_ID>/code/repos?skip_status=true",
"method": "GET",
"message": "You must authenticate with GitHub."
}
- Continue observing the task. Claude may remain stuck or silent while appearing to consume session limit.
- Additional console warnings may also appear repeatedly, including preload warnings, ProseMirror CSS warnings, Intercom / Google Analytics warnings, and a possible EventEmitter listener warning.
Reproducibility
I have observed this behavior after upgrading to Claude 1.6608.2 (ebf1a1). I am not sure whether it reproduces every time, but it occurred while using Claude Code in the macOS app and coincided with repeated GitHub auth_required errors in the console.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.6608.2 (ebf1a1)
Platform
Other
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗