Auten: silent macOS agent failures are TCC, not Claude Code

The piece draws a line between the two permissions a screen-operating agent needs. Accessibility lets it read other apps' UI trees and send synthesized mouse and keyboard events; without it, Accessibility API calls fail with kAXErrorAPIDisabled (-25211) and events sent via CGEventPost are discarded with no error. Screen Recording lets it capture other apps' pixels, and the write-up notes the less obvious loss: other apps' window titles via CGWindowListCopyWindowInfo's kCGWindowName also become unavailable, so even a search for a window by name fails without a single screenshot being taken.

Where the permission lands is described as the point that consumes the most time. macOS attributes the request to a "responsible" app, which for a command-line tool is usually the GUI app that launched it rather than the binary itself. Auten's own case is instructive: it makes an MCP server that supplies "hands" to operate a real screen for any MCP client, covering Mac, Windows and Linux plus Android phones in beta, with a macOS installer that walks through the permission setup and an auten status command that shows what is connected and what is missing. Silent permission errors, it says, were where the company itself first stumbled.