[Bug] Crash when selecting past session in code tab: Error 1YCZHOG
Resolved 💬 16 comments Opened Feb 19, 2026 by svef73 Closed Mar 20, 2026
Bug Description
cowork crashes when selecting a past session in code tab: error code 1YCZHOG
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.47
- Feedback ID: 123a00d6-0c01-4e25-a2f5-70e2162e3849
Errors
[{"error":"AxiosError: Request failed with status code 401\n at _x (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:34:1138)\n at IncomingMessage.<anonymous> (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:35:9827)\n at IncomingMessage.emit (node:events:519:35)\n at endReadableNT (node:internal/streams/readable:1701:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n at Gv6.request (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:37:2132)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async o$6 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:104:3132)\n at async p_A (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:104:8015)","timestamp":"2026-02-19T18:24:48.763Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:482:14)\n at Socket.emit (node:events:507:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-02-19T18:25:00.726Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:482:14)\n at Socket.emit (node:events:507:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-02-19T18:25:58.681Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:482:14)\n at Socket.emit (node:events:507:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-02-19T18:26:08.900Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:482:14)\n at Socket.emit (node:events:507:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-02-19T18:26:09.557Z"},{"error":"RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded\n at Socket.onChildStdout (node:child_process:482:14)\n at Socket.emit (node:events:507:28)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)\n at Readable.push (node:internal/streams/readable:390:5)\n at Pipe.onStreamRead (node:internal/stream_base_commons:189:23)","timestamp":"2026-02-19T18:26:11.521Z"}]
16 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
also seeing this constantly
It's been like this since 10:15AM EST today. Quit Claude desktop, reopen, start working in code... may get 2 mins of work and BOOM back to this screen. Only effecting my desktop connection. Using VSCode Claude plugin has been fine during this time
<img width="745" height="583" alt="Image" src="https://github.com/user-attachments/assets/2342662e-d51c-4a0c-8431-49391ab9380b" />
Getting error code 1YCZHOG any time I try and open certain sessions as well as getting them in new sessions after only a handful of messages requiring low token usage. This has been happening for 2 days now.
+1
This has been happening for 2 days now.
Same here. 24hrs and counting....
Same here. Incredibly frustrating and every time I type in another request I use up a ton of tokens. A full wipe and restart hasn't fixed a thing. New sessions, old sessions, if often crashes after the question, sometimes it gives me 3-4.
Using MacOS, programming in swift, using the desktop app.
same for me.. please ;-((
windows11
since february 18
I am also experiencing this since february 18.
Windows 11,
Claude dektop app,
Claude Code.
Error Code - 1YCZHOG | Crashing since Feb 17, Windows 11
Desktop App - Chat | Cowork | Code - Code keeps crashing, both in previous and current sessions.
Tried everything Uninstalling, Reinstalling multiple times, clearing sessions, Hyper-V/Vmmem spawning on launch, 8 claude.exe processes, no crash logs being written, clearing session data didn't help.
Only Chat mode works smoothly, Cowork & Code crash instantaneously! AI Support are clueless! Human support - No reply!
!Image
Reproducing this on macOS (latest desktop app). Crash logs at
~/Library/Logs/Claude/show the chain clearly:setFocusedSession: sessionId=nullfires when focusing on a chat session1YCZHOGcrash screenAlso seeing
MaxListenersExceededWarning(11$eipc_message$_$_AutoUpdaterlisteners) and preload script errors in the same timeframe.Workaround that helps: Avoid clicking sessions in the sidebar list — instead, use the session search (Cmd+K or the search bar) to open sessions directly. This seems to bypass whatever triggers the
sessionId=nullfocus event that kicks off the crash loop. It doesn't fix permanently corrupted sessions, but it reduces the frequency of new crashes significantly.I found the cause and solution to this issue!!!
`
💪
Found the root cause and fix!
The crash is caused by
.claude/worktrees/being tracked by git. The worktree metadata confuses the session renderer.Fix:
.claude/worktreesto your.gitignore``
``git rm -r --cached .claude/worktrees/
This resolved the
1YCZHOGcrash completely for me.Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.