[BUG] macOS 26.4 Tahoe beta + MCP computer-use checkAccessibility crash
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?
Description
mcp__computer-use__request_access fails immediately with:
Cannot read properties of undefined (reading 'checkAccessibility')
This happens every time, even after reconnecting via /mcp. No permission dialog ever appears.
## Environment
- Claude Code: 2.1.87
- macOS: 26.4 (Tahoe beta, build 25E5223i)
- Terminal: Warp
- Accessibility permission: granted for both Warp and Claude Desktop
- Screen recording permission: granted for both Warp and Claude Desktop
## Reproduction
- Open Claude Code in terminal
- Run
/mcpto confirm computer-use is connected - Ask Claude to use computer-use (e.g. "take a screenshot")
request_accesscall fails with the error above
## Notes
Suspect the Tahoe beta changed or removed an accessibility API that computer-use depends on
internally. The checkAccessibility method is being called on an undefined object, suggesting the
native bridge isn't initializing.
What Should Happen?
request_access should display the permission dialog and grant access to the requested applications,
allowing computer-use tools (screenshot, click, type, etc.) to function normally on macOS Tahoe.
Error Messages/Logs
Steps to Reproduce
- Install Claude Code 2.1.87 on macOS Tahoe 26.4 (beta, build 25E5223i)
- Open Claude Code in terminal (Warp)
- Run
/mcp— computer-use shows as connected - Ask Claude to take a screenshot or use any computer-use tool
request_accessis called and immediately fails with:
Cannot read properties of undefined (reading 'checkAccessibility')
- No permission dialog ever appears
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.87
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
_No response_
This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗