[BUG] Browser control tool (Control_Chrome) always fails on Windows with AppleScript error

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?

On Windows 11, calling any mcp__Control_Chrome__* tool (e.g. list_tabs) always fails with:

Error: AppleScript error: spawn osascript ENOENT

osascript is a macOS-only binary, so this tool appears to be implemented assuming macOS (AppleScript automation) regardless of the host OS. This makes real-browser control completely unusable in this session on Windows.

Notably, a different Claude Code chat session on the same Windows machine has working real-browser (Edge) control, suggesting this may be a per-session/tool-binding issue rather than a blanket platform limitation — i.e., some sessions get bound to a macOS-only browser-control implementation even on Windows.

Steps to reproduce:

1. Start a Claude Code session on Windows.
2. Call any mcp__Control_Chrome__* tool, e.g. list_tabs.
3. Observe: AppleScript error: spawn osascript ENOENT.

Expected: the browser-control tool should either work cross-platform or not be offered/bound in sessions on non-macOS hosts.

What Should Happen?

The mcp__Control_Chrome__* browser control tools should work on Windows, or at minimum should not be bound to a session running on Windows if they only support macOS.

Error Messages/Logs

AppleScript error: spawn osascript ENOENT

Steps to Reproduce

1. Start a Claude Code session on Windows.
2. Call any mcp__Control_Chrome__* tool, e.g. list_tabs.
3. Observe: AppleScript error: spawn osascript ENOENT

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.222 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_