Windows: --chrome native host and channel feature broken for months

Bug Report

Platform: Windows 11 Home (10.0.26300)
Claude Code version: 2.1.114
Shell: Git Bash / PowerShell

---

Issue 1: claude --chrome — Native Host connection fails on Windows

What happens

Running claude --chrome or using the Claude Code Chrome extension integration does not work on Windows. The native messaging host is registered and all infrastructure is in place, but the Chrome extension cannot communicate with Claude Code.

Verified setup (all correct, still broken)

• ✅ Registry key registered: HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension
• ✅ Manifest JSON present: C:\Users\<user>\AppData\Roaming\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json
• ✅ Native host wrapper: C:\Users\<user>\.claude\chrome\chrome-native-host.bat
• ✅ claude.exe exists and runs: C:\Users\<user>\AppData\Roaming\npm\node_modules\@anthropic-ai\claude-code\bin\claude.exe
• ✅ Chrome extension installed (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn, version 1.0.66)

Root cause hypothesis

The .bat file wrapper used for native messaging on Windows has unreliable stdin/stdout handling when Chrome spawns it via Native Messaging protocol. On macOS/Linux, a direct binary is used — Windows requires the .bat → claude.exe indirection which appears to break the stdio communication.

Workaround currently used

Custom Python/Playwright-based MCP server (mcp_computer_chrome.py) as a replacement.

---

Issue 2: Channel feature not working on Windows

What happens

Claude Code channel feature (claude channel) does not function on Windows. Background agents cannot be started or communicated with via channels.

Root cause hypothesis

Claude Code channels rely on Unix domain sockets internally. On Windows, named pipes are used as a substitute, but the implementation appears unstable or broken. This affects persistent background agent workflows entirely.

---

Impact

Both issues have been present for several months with no fix or acknowledgment. Windows users cannot use:

• Chrome browser automation via --chrome
• Persistent background agents via channels

These are core Claude Code features that work seamlessly on macOS but are completely non-functional on Windows.

Request

1. Official acknowledgment of Windows --chrome native messaging bug
2. Fix the .bat wrapper stdio handling, or provide a native .exe host for Windows
3. Fix or document the Windows channel/named pipe limitation
4. Add Windows to CI/CD test matrix to prevent regressions

---

Reported from a Windows 11 production environment where Claude Code is used daily for research automation.