Claude Code Closes a Computer-Use Permission Gap on macOS
Claude CodeClaude Code's macOS computer-use feature previously let Claude click the desktop, the Dock, or a Finder window without first prompting for the same per-app access grant required for every other application. Claude Code 2.1.243 closes that gap: interacting with the desktop, Dock, or Finder now requires the standard Finder access-dialog grant, matching how every other app is handled. This is a trust-boundary fix, since it removes a path where Claude's on-screen actions were not gated by the permission prompt users rely on to control what it can touch.
Key Takeaways
- Clicking the desktop, Dock, or Finder previously bypassed the per-app access dialog that governs every other application in computer use.
- The fix requires an explicit Finder grant before Claude can interact with those three surfaces, matching how all other apps are already handled.
- This is a permission-boundary fix, not a new feature: it closes a gap rather than adding capability.
- Finder access is significant because it exposes the filesystem visually, making the previous gap a meaningful blind spot in what required consent.
- No other computer-use behavior changed: apps that already required the access dialog still do, unchanged.
- The fix shipped in Claude Code 2.1.243, released August 24, 2026, in a release otherwise focused on reliability and performance.
A Quiet Gap in Computer Use, Closed
Claude Code's computer-use feature on macOS lets Claude see and interact with the screen, clicking, typing, and navigating apps on the user's behalf. Every app Claude reaches through computer use is normally gated behind a per-app access dialog, similar to macOS's own Accessibility or Screen Recording prompts, so a person can see and control exactly which applications Claude is allowed to touch. Until this release, three specific surfaces, the desktop itself, the Dock, and Finder windows, were an exception: Claude could click into them without that access dialog ever appearing.
What Changed
Claude Code 2.1.243 removes the exception. Clicking the desktop, the Dock, or a Finder window through computer use now requires granting Finder through the access dialog first, exactly as clicking into any other application already did. Nothing about the underlying computer-use capability changed, and nothing users could already deny remains deniable; what changed is that a specific set of interactions that had bypassed the per-app gate now goes through it like everything else.
Why This Belongs in the Security Column
This falls squarely into the category of permission-boundary fixes: it closes a path where Claude's on-screen actions were not covered by the access control users were relying on. Desktop, Dock, and Finder interactions are a meaningful surface, since Finder in particular exposes the filesystem visually, so a gap there meant part of a user's screen was reachable by Claude without the explicit grant that governs everything else computer use can touch. Anthropic's fix brings that surface under the same consent model as the rest of the feature.