[BUG] Claude Code CLI freezes when VSCodium extension is installed (Windows)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

See additional information below

What Should Happen?

See additional information below

Error Messages/Logs

Steps to Reproduce

See additional information below

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.5

Platform

Other

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

---
Title:

Claude Code CLI freezes when VSCodium extension is installed (Windows)

Body:

## 🐛 Bug Description

Claude Code CLI (native v2.0.5) freezes and blocks user input when VSCodium extension (v2.0.1) is
installed, even when VSCodium is completely closed. This affects all Windows terminals (PowerShell,
CMD, Git Bash) but not WSL or the VSCodium extension itself.

## 🔄 Steps to Reproduce

1. Install Claude Code native CLI (v2.0.5)
2. Install VSCodium with Claude extension (v2.0.1)
3. Use Claude extension in VSCodium (creates conflicting config files)
4. Close VSCodium completely
5. Launch claude in any Windows terminal
6. Result: CLI appears to start but freezes with no input prompt

## 🎯 Expected Behavior

Claude CLI should launch normally and display authentication prompt or chat interface.

## 🚨 Actual Behavior

• Claude CLI appears to start
• Terminal hangs with no visible prompt
• No response to keyboard input
• Must force-quit with Ctrl+C

## 💻 Environment

• OS: Windows 11 with WSL2
• Claude Native: v2.0.5
• VSCodium Extension: v2.0.1
• Claude Plan: Pro
• Affected Terminals: PowerShell 5.1, PowerShell 7+, CMD, Git Bash
• Working Environments: WSL Ubuntu, VSCodium extension interface

## 🔍 Root Cause Analysis

The issue is caused by version incompatibility between CLI and extension creating conflicting files in
~/.claude/:

• ~/.claude/ide/ directory with lock files (created by extension)
• ~/.claude/shell-snapshots/ with incompatible configurations
• Session files containing "version":"2.0.1" metadata that CLI v2.0.5 cannot process

## 🛠️ Workaround Available

I've created community workarounds while waiting for an official fix:

Repository: https://github.com/mistyczorg-creator/claude-vscodium-conflict-fix

Quick fix:
```powershell
# Download claude-simple.ps1 and run:
.\claude-simple.ps1 -Login

The workaround cleans conflicting files and forces re-authentication to bypass the freeze.

📋 Additional Notes

• Issue is Windows-specific (WSL environments unaffected)
• Occurs even when VSCodium is fully closed
• Simply disabling the extension is not sufficient
• Both CLI and extension work fine independently

⚠️ Impact

This prevents users from using both Claude interfaces simultaneously on Windows, forcing them to
choose between CLI or VSCodium extension.

---
Labels suggestion: bug, Windows, auth, core