Perplexity brings local-first Windows agents to high-end RTX PCs, with privacy and benchmark questions unresolved

Documented capabilities. Perplexity’s product page says Portable Computer can run local agents, schedule recurring tasks, use local files, call Perplexity Search, connect to services such as Gmail, Outlook, Slack, and GitHub, and route specific steps to cloud models after approval. Portable Computer: Local-First AI NVIDIA similarly says the Windows app supports local analysis across files, recurring work, cloud escalation with user permission, a built-in browser, a sandbox, and connectors for Microsoft Outlook, OneDrive, Word, Google Drive, Gmail, Slack, and GitHub. Perplexity Portable Computer Is Now Available on Windows, Powered by NVIDIA RTX | NVIDIA Blog

Access requirements. Perplexity’s setup page says Windows users need a supported NVIDIA RTX GPU with 24GB VRAM or higher, must start with Personal Computer for Windows, and then enable PPLX 27B local inference in Settings; it also says only one local model runs at a time. Portable Computer: Local-First AI Tom’s Hardware independently reported the same 24GB VRAM and Pro/Max subscription requirements. Perplexity’s local AI agent comes to Windows, but only for RTX GPUs with at least 24GB of VRAM — Portable Computer brings AI for multistep tasks to compatible PCs | Tom's Hardware

Exact model/version. The clearest current Perplexity setup statement is: Windows RTX PCs: PPLX 27B available; Qwen 3.8 27B not available; NVIDIA Nemotron 3.5 Lightning coming soon. Portable Computer: Local-First AI However, NVIDIA’s launch blog says the app simplifies setup with “a local model, such as Qwen 3.8 27B,” post-trained for Perplexity Computer and optimized for RTX GPUs. Perplexity Portable Computer Is Now Available on Windows, Powered by NVIDIA RTX | NVIDIA Blog Treat this as a product-documentation mismatch unless Perplexity clarifies whether NVIDIA is referring to the base model behind PPLX 27B or to an option not reflected on Perplexity’s setup page.

Architecture, as documented. Portable Computer appears to bundle four layers that open-source local-agent users often assemble manually: local inference, an agent harness, tool/connectors, and sandboxed execution. Perplexity describes the local stack as running the harness, orchestrator, planner, and tool router locally with 27B-class models; cloud escalation is a per-step workflow where the orchestrator asks before routing a task to external models. Portable Computer: Local-First AI

Implementation implications. For developers, the interesting design decision is not simply “local LLM on GPU,” but the co-design of model and harness. Perplexity’s product materials indicate a local orchestrator controls GitHub/Slack-style tasks, keeps a receipt-like run record, and asks before posting externally or searching the web. Portable Computer: Local-First AI NVIDIA says Perplexity also uses a proprietary SPACE sandbox and built-in browser, while code/tool execution runs in isolated environments with controlled access to local files and apps. Perplexity Portable Computer Is Now Available on Windows, Powered by NVIDIA RTX | NVIDIA Blog

Evaluation methodology. Publicly visible benchmark evidence remains mostly vendor-run. Perplexity-reported results cited in secondary analysis describe a Local Knowledge Work Bench with 53 tasks across knowledge-work categories; reported scores include PPLX 27B ahead of Qwen 3.8 27B in the Perplexity harness, but these results were run on DGX Spark-class hardware and had not been independently reproduced in the sources found. PPLX 27B — AI Stack Current VentureBeat also notes Perplexity characterized the benchmark as internal and planned for open-sourcing, which means today’s numbers should be treated as claims, not reproducible evidence. Perplexity partners with Nvidia to launch Portable Computer, a fully local AI agent with zero token costs | VentureBeat

Reproducibility. No independent Windows RTX benchmark suite, no published red-team report for the Windows Portable Computer sandbox, and no public artifact sufficient to reproduce Perplexity’s exact local-agent benchmark on Windows were found in the reviewed sources. The closest user-level technical report was a Reddit post from a DGX Spark user claiming the install downloaded a large Docker/vLLM image and a 27GB PPLX model, but that is anecdotal and not controlled evaluation. Feedback on Perplexity Portable Computer with local inference : r/perplexity_ai

This launch fits a broader move from chatbot interfaces toward agentic desktop workflows: agents can read files, use apps, click/type/scroll, invoke connectors, and run in background workspaces. Microsoft’s Windows agentic-feature documentation frames this as powerful but risky, emphasizing scoped authorization, separate agent accounts, audit logs, user supervision, and least privilege. Experimental Agentic Features | Microsoft Support

Perplexity is also not alone in pushing local or hybrid AI. The differentiator it claims is product integration: users do not have to separately choose weights, configure inference, wire MCP servers, and build sandboxing. Tom’s Guide described that bundling as the hard part of turning a local model into a usable multistep agent. Perplexity’s new local-first AI runs on your PC — and asks before using the cloud | Tom's Guide

Privacy boundary. “Runs locally” is not the same as “private by design.” A local agent may still index or summarize sensitive files, log actions, retain derived state, use connectors, or send selected context to cloud models after approval. The strongest governance posture would require observable file-access scopes, retention controls, egress logs, connector-specific permissions, and auditable fallback decisions. Local Is Not a Sufficient Privacy Boundary: Governing OS-Integrated On-Device AI

Prompt injection and delegated action. Microsoft explicitly warns that agents interacting with UI elements and documents face cross-prompt injection risks that can lead to unintended actions, including data exfiltration or malware installation. That concern applies conceptually to any desktop agent that reads untrusted documents or web pages and can take actions. Experimental Agentic Features | Microsoft Support

Hardware exclusion. The 24GB VRAM floor excludes most consumer Windows PCs. Tom’s Hardware notes compatible consumer cards include high-end SKUs such as RTX 3090/4090-class cards, making this more relevant to developers, AI teams, and workstation users than ordinary office laptops. Perplexity’s local AI agent comes to Windows, but only for RTX GPUs with at least 24GB of VRAM — Portable Computer brings AI for multistep tasks to compatible PCs | Tom's Hardware

User friction. Reddit user reports are not rigorous evidence, but they flag adoption risks: one user complained Perplexity was intrusive about file access, while another reported bugs/ambiguity around custom inference endpoints. These are anecdotal but relevant for product rollout risk. I will stop using Perplexity after my free Pro plan ends because it keeps intrusively asking for access to all files on my PC : r/perplexity_ai

For businesses with compatible GPUs, Portable Computer could be useful for sensitive document summarization, codebase review, recurring report generation, and local-first analysis of finance or customer-data exports—especially where uploading raw files to a chatbot is disallowed. NVIDIA gives examples across engineering, finance, and startup analytics, but those are vendor examples rather than audited case studies. Perplexity Portable Computer Is Now Available on Windows, Powered by NVIDIA RTX | NVIDIA Blog

For CIOs and security leaders, the procurement question is not “cloud or local?” but “what is the agent’s authority model?” Require documentation for folder scopes, connector scopes, audit logs, sandbox boundaries, cloud-escalation prompts, retention/deletion behavior, telemetry, and enterprise controls before deploying against regulated or client-confidential data.

For developers, the product is a signal that local agents are becoming less about raw model serving and more about harness quality, tool mediation, sandboxing, and routing policy. If Perplexity open-sources or documents its benchmark, it could become useful for comparing local-agent stacks; until then, the reported performance claims should not drive architectural decisions alone.