Orply.

Perplexity Brings Computer Agent Workflows Into the Mac Desktop

PerplexityFriday, June 26, 20266 min read

Perplexity Academy presents Personal Computer as a Mac-based extension of Perplexity Computer, designed to let the system act on the files, apps, folders, browser tabs, and desktop context where users’ work already sits. The tutorial argues that the product’s significance is local access: users can start tasks from the Mac app, a floating desktop bar, voice mode, remote control, or Comet, while heavier processing remains on Perplexity’s servers. Its examples frame the Mac not as an endpoint for AI output, but as an operating surface for organizing folders, updating files, reviewing presentations, generating briefs, and running recurring background work.

The Mac is the work surface, not just the endpoint

Personal Computer is presented as a way to bring Perplexity Computer into the local Mac environment, where much of a user's work already exists: files, desktop apps, browser tabs, and everyday tools. The central claim is not that it replaces the cloud version of Computer, but that it gives Computer access to the context that sits outside a chat box.

Perplexity’s examples are ordinary but hard to contain inside a prompt-only interface: messy folders, repeated workflows, app-based tasks, and projects that need Computer to keep working in the background. Personal Computer is meant for tasks whose inputs and outputs already live on the machine — a folder that needs organizing, a file that needs updating, a presentation that needs review, or a recurring workflow that should not require the user to manually shuttle information between apps.

Perplexity describes the product as built into the Perplexity Mac app. The setup path is direct: download Perplexity for Mac from perplexity.ai/personal-computer, install the app, and run it on a Mac using macOS 14 Sonoma or later. The product page shown in the source states: “Personal Computer is here. Run Personal Computer on any Mac through the Perplexity macOS app.”

macOS 14
minimum Mac operating system named for Personal Computer support

Local access changes what Computer can act on

Perplexity distinguishes between Computer running tasks in the cloud and Personal Computer adding access to the local machine. Cloud Computer is shown with connectors that let Perplexity access and act on data in connected services; Personal Computer extends that operating surface to the Mac itself, including files, apps, and the desktop environment.

That local access is the enabling mechanism. With permission to use local files, Computer can read, write, and search files and connected folders directly on the Mac. The demonstrated prompt asks it to “summarize all documents in this folder and group them by project,” with a folder named “Q3 Product Launch” selected through the interface. The point is not simply document summarization; it is that the folder is local, selected from the Mac, and treated as actionable workspace rather than as an attachment manually copied into a chat.

The same pattern appears with a more complete local-file task: “Create a Q3 product launch brief as a PDF using all relevant files about the new product in my Documents and Downloads folders.” The resulting interface shows a product launch folder summary and a generated file named “Aurora Q3_Launch_Brief.” The workflow shown is: search across local folders, identify relevant material, synthesize it, and produce a PDF output.

Perplexity’s product description draws the division of labor this way: Personal Computer reaches into the local Mac environment, while heavy processing still runs on Perplexity’s secure servers. The tutorial’s emphasis is on what the Mac app adds to Computer’s operating surface — direct access to local files, connected folders, native apps, and the desktop environment.

The interface is designed to avoid switching contexts

Personal Computer is shown as something accessible from wherever the user is already working on the desktop. A shortcut summons a floating task bar, allowing the user to describe a task without moving into a separate full-screen chat or manually gathering context first.

One example overlays the floating task bar on a Keynote presentation. The visible prompt says: “Take a look at my presentation and suggest three improvements to the flow.” That example matters because the task is app-based: the object of work is not a document pasted into a prompt, but an open presentation on the desktop. Personal Computer is being positioned as able to inspect or work with what is already in view and respond to a task about it.

Voice mode is presented as another entry point. The user can speak naturally to the Mac, and Computer can understand the request and act on it. The demonstrated voice request is more complex than a reminder or search query: “Look at my calendar for tomorrow, pull the latest email thread with each attendee, and write me a one-page brief for each meeting with talking points and any open questions I owe them.”

The system response shown is: “The task to draft those briefs is underway. I'll let you know when it's finished.” The example combines calendar context, email retrieval, synthesis, and writing. It also implies asynchronous execution: the user starts the job, and Computer continues working rather than requiring the user to remain inside the interface.

Always-on use turns a Mac into a background worker

Perplexity also presents Personal Computer as useful for always-on work. On a Mac mini, Computer can keep running in the background around the clock, even when the user is away. The visual example shows a Mac mini and monitor with background tasks labeled “Snowflake DAU Pull,” “Github PR Fetch,” “Follow Up Email,” and “Task.”

The examples are operational rather than abstract. They point to recurring background work: pulling a metric, fetching GitHub pull requests, preparing follow-up email, or continuing a task without the user sitting at the keyboard. The tutorial does not expand those examples into a detailed system design; it uses them to show the intended pattern of a Mac that remains available for ongoing work.

Remote control extends that idea beyond the desk. Tasks can be started and managed from an iPhone or another device while the Mac keeps working. The demonstrated task asks Personal Computer to “Find every receipt in my Downloads from the last 30 days and put them in a folder called Q2 Expenses.” The task is initiated or monitored across devices, but the work remains anchored to the Mac's local filesystem.

That framing is important: remote control is not presented as a separate mobile agent. It is a way to direct the Mac from elsewhere. The Mac remains the machine with the files, apps, folders, and running environment that Personal Computer can act on.

Comet adds the browser to the same operating surface

Perplexity pairs Personal Computer with Comet, its browser, so Computer can browse, research, and automate web tasks from the same environment.

The demonstrated web task asks Computer to visit a Kitchen Depot product page, grab pricing for every product, and create a comparison table against the user's prices to identify gaps. The following screen shows the Kitchen Depot page and a “Kitchen Depot Pricing Comparison” table being generated. The example shows the intended bridge between browser automation and workplace output: navigate to a site, extract information, structure it, and compare it against existing pricing data.

In Perplexity’s product logic, Comet is not a separate destination but another surface Personal Computer can work through. Local files, desktop apps, browser tabs, connected folders, and web research are all presented as parts of one environment where Computer can receive an instruction and carry out the work.

The frontier, in your inbox tomorrow at 08:00.

Sign up free. Pick the industry Briefs you want. Tomorrow morning, they land. No credit card.

Sign up free