[Bug] CLI freezes on startup during initial prompt input before IDE message loads
Status Fixed / completed
Reported on v2.1.51
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 5 comments · opened Feb 24, 2026 · closed Mar 9, 2026
Bug Description
When Claude Code launches and you start typing your prompt it freezes for a few seconds then starts working again. It feels like blocking behaviour as it occurs right before the message that states " /ide for Visual Studio Code" loads and once loaded is when it starts responding again.
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.1.51
- Feedback ID: b602af2b-bf6c-4be8-8502-6b0ed60af112
Errors
[{"error":"Error: ENOENT: no such file or directory, open '/Library/Application Support/ClaudeCode/managed-settings.json'\n at openSync (unknown)\n at readSync (/$bunfs/root/claude:12:1441)\n at F2 (/$bunfs/root/claude:6412:113)\n at AO (/$bunfs/root/claude:6414:226)\n at GP8 (/$bunfs/root/claude:6398:5806)\n at s90 (/$bunfs/root/claude:6398:5579)\n at <anonymous> (/$bunfs/root/claude:6398:4272)\n at async a90 (/$bunfs/root/claude:6398:4654)\n at async <anonymous> (/$bunfs/root/claude:11966:400)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-24T04:03:30.814Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/samm/.local/share/claude/versions/2.1.51 (expected in multi-process scenarios)\n at aPR (/$bunfs/root/claude:3745:2100)\n at HvA (/$bunfs/root/claude:3745:1820)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-24T04:03:30.886Z"}]
5 Comments
same for me (so not filing a dupe)
(file:///home/runner/work/claude-cli-internal/...) baked into extension.js
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
on reflection, my issues is not this one
Seems to be fixed now?
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.