Perplexity Computer: Testing Parallel AI Workflows

Perplexity Computer is a cloud agent you assign to a task and step away from. Since its February 2026 launch, updates have changed who can access it, how credits are tracked, and how much control you get before a run starts. That makes many early reviews dated.

I tested a parallel research workflow across eight AI coding tools, using a fixed prompt and a visible credit total. The result gave me enough to judge the pricing, the limits, and the plan choice together.

What Is Perplexity Computer and How Does It Work?

Computer is Perplexity's cloud-based agent product. It is not a device, and it is not the same thing as Perplexity Ask. Ask returns answers. Computer takes actions: it browses the web, generates documents and slides, runs code in a sandbox, hits hundreds of connectors, and chains those steps into a finished output.

There is a separate product called Personal Computer that runs locally on a Mac. It launched in mid-April 2026 and is rolling out from Max to Pro. This review is about the cloud Computer.

Computer task composer on Perplexity web. Image by Author.

The architecture matters because it shapes the cost story. Computer drafts a plan, then routes steps to specialized sub-agents inside an isolated cloud sandbox. As of the May 4, 2026 update, GPT-5.5 is the default orchestrator for Pro and Max subscribers, so launch-era references to Claude Opus 4.6 as the default are stale.

For research tasks, "parallel execution" refers to how Computer searches and splits work. A single research sub-agent can run seven search types at once: web, academic, people, image, video, shopping, and social, reading full source pages instead of snippets. Multiple sub-agents can also run inside one task. For Max users, Model Council adds a separate model cross-check for questions where disagreement matters.

Two later additions matter for this review: plan previews before long tasks, and live cost tracking during execution. Those controls let me track the run instead of judging cost afterward.

Regular Perplexity Ask searches and Deep Research do not consume credits. Computer tasks do.

Perplexity Computer Pricing: Pro, Max, and How Credits Work

Computer billing has two parts: a flat subscription plan, plus a separate credit balance the agent draws down as it runs. Read them together, or the real cost is hard to judge.

Here is the current consumer and enterprise pricing as of early May 2026. Verify the figures on the day you sign up, since pricing and credit rules can shift by region, plan, or promotion.

Two details usually get glossed over. Pro gives access but no monthly Computer credits, so users need purchased credits or auto-refill. Max includes 10,000 monthly credits, plus current one-time bonus credits for paid Pro and Max signups, per the official help center page on credits. Treat bonuses as temporary because they can change and expire.

Credit cost varies by task, and Perplexity does not publish a per-task table. Simple jobs can cost tens of credits; research-heavy tasks can run into the hundreds or thousands; failed coding loops have crossed 10,000. Auto-refill is off by default, monthly credits do not roll over, and active tasks pause if you run out.

Testing Parallel Execution: A Real Research Workflow

Here is the actual test. I asked Computer to research eight AI coding tools, collect the same fields for each one, flag contradictions, and turn the results into a comparison table plus a short memo. I picked this case because it tests parallel research without drifting into open-ended coding work, where credit use is harder to control.

Before the prompt, a few prerequisites need to be in place.

Prerequisites and account setup

The test ran on Max for the credit allowance. As mentioned earlier, Pro users can run the same workflow with purchased credits. No special connectors are required for a research-only task. You need:

• An active Perplexity subscription with Computer access, meaning Pro or Max
• A credit balance high enough to cover the run, ideally at least 1,500 credits to leave headroom for revisions
• A clear list of targets written down before the run starts, rather than leaving scope open for Computer to interpret

The Computer panel opens from the home page on web, from the Computer tab on iOS, and from the Perplexity desktop app on Mac.

How to write a prompt that triggers parallel execution

Prompt design matters because Computer turns your instructions into sub-agent work. A vague prompt produces a vague run. This one fixes the targets, fields, citation rule, memo audience, and pause point.

Research the following 8 AI coding tools in parallel: GitHub Copilot, Cursor,
Claude Code, Windsurf, Aider, Continue.dev, Tabnine, and Cody.

For each tool, collect the same fields:
Pricing for individual paid plansCore features, with a focus on agent behaviorMain use casesTwo main limitationsOne notable update from the past 90 daysA primary source link for every important claim
Then:
Build a single normalized comparison tableFlag any field where two of your sources contradict each otherWrite a 200-word recommendation memo for a senior backend engineer who already pays for one AI coding tool and is considering whether to switch
Before producing the final memo, show the plan, the list of sources you intend to cite, and your credit estimate, then wait for my approval.

Two design choices matter most. The plan preview gives you a chance to narrow scope before credits are spent. The "flag contradictions" line pushes Computer to surface disagreements instead of flattening them into one answer.

Running the workflow with plan preview and live credits

After submitting the prompt, Computer paused on a written plan that listed the eight target tools, the data sources it intended to use, the order of work, and a rough credit estimate. Approving the plan started the parallel research phase, and the live credit counter began ticking up in the thread. That counter, added in the March 27, 2026 update, became the number I watched most closely.

Plan preview before approving the run. Image by Author.

Sub-agents ran across the eight tools at the same time. The activity panel showed progress lines with brief notes on which sites were being read. One sub-agent paused mid-run to ask whether to count a company's open-source CLI as a separate product. That kind of interrupt matters because early reviews described Computer as a black box. As of the April 17, 2026 update, you can stop a single sub-agent or type a follow-up instruction mid-task.

The full run took 7 minutes 59 seconds and consumed 225.71 credits. That number will not match yours. Agent runs are non-deterministic: the same prompt produces a different decomposition, a different model assignment, and a slightly different output on each run. If you are recording for a video or a demo, do a dry run before the real one.