[Bug] VS Code extension session terminates immediately after SessionStart
Resolved 💬 3 comments Opened Jan 31, 2026 by blumekt Closed Feb 4, 2026
Bug Description
VS Code extension session terminates immediately after SessionStart.
Logs show: SessionStart → SessionEnd within 200ms, before any message is processed.
CLI works fine. Only VS Code extension affected. Version 2.1.27 Windows.
Steps: Open Claude Code panel → Type message → "Frolicking..." forever → No response
Environment Info
- Platform: win32
- Terminal: vscode
- Version: 2.1.27
- Feedback ID: 8e565573-8b1e-4c89-8c34-397484e3a0e5
Errors
[{"error":"AbortError: The operation was aborted.\n at unknown\n at abortChildProcess (node:child_process:947:42)\n at onAbortListener2 (node:child_process:35:24)\n at abort (unknown)\n at <anonymous> (B:/~BUN/root/claude.exe:3070:209)","timestamp":"2026-01-31T16:03:55.295Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at I (B:/~BUN/root/claude.exe:73:189)\n at <anonymous> (B:/~BUN/root/claude.exe:73:403)\n at exitHandler (node:child_process:109:27)\n at errorHandler (node:child_process:118:16)\n at emitError (node:events:43:23)\n at abortChildProcess (node:child_process:947:17)\n at onAbortListener2 (node:child_process:35:24)\n at abort (unknown)\n at <anonymous> (B:/~BUN/root/claude.exe:3070:209)","timestamp":"2026-01-31T16:03:55.296Z"}]This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗