CLI Hangs/Terminates Silently Without Error Output
Status Fixed / completed
Maintainer reply None cached
Activity 10 comments · opened Jul 17, 2025 · closed Jul 18, 2025
Bug Description
just stop executing without any feedback
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 1.0.54
- Feedback ID: 90d234b1-c947-4d79-9c98-a28e1ab27d96
Errors
[{"error":"Error: Command failed: security find-generic-password -a $USER -w -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n at genericNodeError (node:internal/errors:984:15)\n at wrappedFn (node:internal/errors:538:14)\n at checkExecSyncError (node:child_process:889:11)\n at execSync (node:child_process:961:15)\n at DI (file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:730:2037)\n at file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:640:41635\n at Q (file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:542:14406)\n at PF (file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:640:39420)\n at $X (file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:640:38286)\n at MB (file:///Users/gam0161/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:640:44255)","timestamp":"2025-07-17T05:10:24.472Z"}]
10 Comments
+1
Downgrade to
1.0.52helps (npm install -g @anthropic-ai/claude-code@1.0.52and the do not forget to disable autoupdate).for developers: please mark 1.0.53 and 1.0.54 as next and move stable to 1.0.52, not working CC is not a good start for a working day :)
+1
+1
same, they are almost there
<img width="970" height="276" alt="Image" src="https://github.com/user-attachments/assets/2267dd8f-09b1-447a-8bb8-74343a233059" />
<img width="1024" height="1536" alt="Image" src="https://github.com/user-attachments/assets/4638adfe-284c-4134-af4c-9bca2b87df37" />
oh, it works now, but still do not have any ideas what happened
Still broken
+1
^^^ because first 1.0.53 was marked as stable, and now 1.0.52 marked as stable, and in you case auto-update looks like updated the app. That's why it may start working. Check version :)
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.