Perplexity has introduced Portable Computer, a local-first version of its agentic Personal Computer. The agent executes AI tasks on the user's machine, running models, handling files, and completing assignments inside an isolated sandbox. Users control if and when the agent needs cloud access to finish tasks or fetch external data.
Three concrete advantages of local execution are performance, security, and cost. Local models can respond faster than cloud-hosted frontier models because inference happens on-device. Data processed by the agent stays on your machine unless you explicitly permit cloud access, reducing the surface for data exposure. And local inference does not consume cloud credits or tokens, so only actions that require going online will incur billing costs.
Local AI is resource-intensive and Portable Computer reflects that. On Linux, Perplexity requires an NVIDIA DGX Spark or other machine with an NVIDIA RTX GPU, running Nvidia DGX OS or Ubuntu on ARM or x64. Windows support will demand an NVIDIA RTX GPU with at least 24GB of VRAM. Lower-end desktop GPUs (for example, those with 4GB VRAM) will not meet the threshold. High-VRAM RTX cards carry significant cost, so adopting Portable Computer may require new hardware purchases for many users.
Portable Computer supports at least two model options. Qwen 3.8 27B is an open-weight model noted for speed and capability across coding, research, and other complex agentic tasks. Perplexity also offers PPLX 27B, a post-trained variant the company applies to Portable Computer to sharpen accuracy and efficiency for agent workloads. Perplexity plans to add Nvidia's Nemotron 3.5 Lightning for heavy-volume or long-running tasks. Users can switch models based on the assignment and their hardware constraints.
How it interacts with cloud services Even when running locally, Portable Computer can access cloud services such as Google Drive, Gmail, Slack, and GitHub to pull in remote files or accounts when the user permits. Perplexity's model routes allow the agent to keep sensitive data local while still using cloud resources where needed, with only the cloud portions consuming credits.