The Perplexity Personal Computer Mac alternative that runs the agent loop on your machine, not theirs

It is Perplexity's AI orchestration layer for macOS, launched on April 16, 2026 as a Max-only feature and opened to all Pro and Enterprise users on May 7, 2026. It accesses your file system and native Mac apps to execute multi-step workflows, with intensive tasks routed to Perplexity's servers and files written into a sandbox. It requires macOS 14 Sonoma or later and a Pro or Max subscription, and is distributed as a direct download (not via the Mac App Store).

Three reasons keep coming up. The agent loop runs on Perplexity's infrastructure for anything 'intensive,' which means your screen context and the actions taken on your behalf travel through their stack. The product is closed source and there is no public technical disclosure of how it controls your Mac apps. And it requires a paid subscription tier (Pro at $20/mo or Max at $200/mo) for the agent feature itself, not just the model. None of those are problems if they fit how you work; some people care about all three.

Locally. The Swift app spawns a Node subprocess (acp-bridge) that hosts the agent loop. That bridge spawns the MCP toolchain (playwright, macos-use, whatsapp, fazm_tools, google-workspace) as further local subprocesses. Tool calls block on those local processes synchronously. The model endpoint is pluggable and the only thing that crosses the network. Read AppState.swift and ACPBridge.swift in the open source repo to verify.

Through the macOS Accessibility framework. Specifically, AXUIElementCreateApplication takes a local PID, AXUIElementCopyAttributeValue reads named attributes like kAXFocusedWindowAttribute, and the macos-use MCP traverses the resulting element tree. The same APIs Apple ships for assistive technologies. There is no remote variant of these calls; they only work from a process running on the same macOS instance as the windowserver.

A 1920x1200 screenshot is on the order of 350,000 image tokens for the modern Anthropic tokenizer. The accessibility tree of a single Mail window is around 1,500 text tokens. Ten turns of screenshots is roughly 3.5 million pixel tokens before the model thinks; ten turns of AX trees is roughly fifteen thousand. That is not a marketing claim, it is what counting tokens looks like.

Most of them, yes. Anything exposed via macOS Accessibility (Mail, Notes, Slack, Safari, Calendar, Reminders, third-party apps that implement AX) plus everything in a real browser via the Playwright MCP. Google Docs, Sheets, Calendar work through the Apps Script integration. The one thing Personal Computer ships that Fazm does not is Comet browser integration, since Comet is a Perplexity product.

Sandbox plus auditable actions plus a kill switch is a fine design choice. The honest read is that those are claims a closed binary makes about itself; you take the vendor's word for it. With Fazm the audit is the repository: every file that touches accessibility, the screen, your microphone, or your local data is in the open. That is a different shape of trust, not necessarily a stronger one for every user.

Yes if you only want the agent. Fazm hosted is $9.99/mo with no free trial; building from source is free. Perplexity Pro is $20/mo and bundles the agent with the chat product. Max is $200/mo and was the original tier required for Personal Computer. If you already pay for Perplexity Pro for search, you are paying once; if you signed up for Pro mostly for Personal Computer, the math changes.

That is a sensible split. Perplexity is excellent at conversational web search and AI overviews; Fazm is built for the cycle of voice in, agent operates the apps you already use, voice or text out. They are not exclusive. Run both, route different intents through different products.

Perplexity Personal Computer launch coverage: macrumors.com (April 16 and May 7 2026), techcrunch.com (May 7), 9to5mac.com (May 7), cultofmac.com on the hybrid cloud-local architecture and Pro/Max subscription gate. Fazm source: github.com/m13v/fazm, with AppState.swift line 480-534 covering the AX probe and the Finder fallback.