VSCode Extension crashes with exit code 1 during webview operations

Description

Claude Code VSCode extension repeatedly crashes with exit code 1 during routine webview operations (tab renaming, session retrieval).

Environment

• Extension Version: 2.1.27
• VSCode: Remote - Containers (GitHub Codespaces)
• OS: Linux 6.8.0-1030-azure
• Platform: linux-x64

Error Log

2026-01-31 14:18:47.423 [info] From claude: 2026-01-31T14:18:47.423Z [DEBUG] [API:auth] OAuth token check complete
2026-01-31 14:18:47.437 [info] Received message from webview: {"type":"request","requestId":"0qzvkmj1i93i","request":{"type":"rename_tab","title":"Gr-Goldsage Convo 1.  Pl…","hasPendingPermissions":false,"hasUnseenCompletion":false}}
2026-01-31 14:18:47.437 [info] Received message from webview: {"type":"request","requestId":"y8j7lx73hg","request":{"type":"get_session_request","sessionId":"0b521191-d592-4405-a84e-a9bb5b7f6f81"}}
2026-01-31 14:18:47.660 [info] Closing Claude on channel: ed2w73eeq1n
2026-01-31 14:18:47.660 [error] Error from Claude (on channel ed2w73eeq1n): Error: Claude Code process exited with code 1

Pattern

1. OAuth token check completes successfully
2. Webview messages received (rename_tab, get_session_request)
3. Process crashes with exit code 1
4. 14+ minute gap before next activity (extension becomes unresponsive)

System Resources (at time of crash)

• Memory: 31GB total, 24GB available (not memory pressure)
• Disk: 246GB available on /tmp
• Multiple Claude processes running (expected for parallel operations)

Hooks Configuration

Using custom hooks via .claude/settings.json for SessionStart, UserPromptSubmit, PostToolUse, Stop, and SessionEnd. However, hooks execute successfully (confirmed via system-reminder messages showing "hook success: Success").

Frequency

Happens repeatedly during normal usage, not a one-time occurrence.

Steps to Reproduce

1. Open Claude Code in VSCode (Codespaces environment)
2. Start a conversation
3. Use the extension normally
4. Crash occurs during tab rename or session retrieval operations

Additional Context

The crash appears to happen during internal webview<->extension communication, specifically when processing rename_tab or get_session_request messages. The channel-specific error suggests possible channel lifecycle management issues.