What happened
On August 25, 2026, Perplexity launched Portable Computer, a version of its agentic Computer platform that runs entirely on hardware a user already owns. Built in partnership with Nvidia, it targets the DGX Spark desktop supercomputer and Linux machines with RTX GPUs. Users can pick Qwen 3 27B or PPLX 27B locally at launch, with Nvidia's Nemotron 3.5 Lightning arriving soon. Every task starts on the device by default. The system asks permission before sending any individual step to a more powerful frontier model in the cloud. Work completed locally consumes no billing credits, and the model, files, and outputs can all stay on the machine. It ships day one to Pro, Max, Enterprise Pro, and Enterprise subscription tiers. The company frames the product as a bet that serious agent workloads belong on the device, not in a data center.
Why the local-first AI agent matters now
MagnetizeX builds founder visibility systems for B2B firms.
For B2B buyers, the shift is quiet but structural. A research query run on a local model does not touch Perplexity's servers, which means it does not become telemetry, and it does not feed the cross-vendor visibility dashboards founders currently pay to track. When a competitor's CEO researches your positioning on a locked-down laptop, no citation platform can see the query, and no attribution tool can see the answer. The vendor-selection layer is quietly moving out of view for anyone measuring share of voice inside AI answer engines. That changes both what you optimize for and what you measure.
By the numbers: Portable Computer launches with two 27-billion-parameter model options at zero per-token cost on local steps, ships day one to Pro, Max, Enterprise Pro, and Enterprise tiers, and adds Nvidia Nemotron 3.5 Lightning support within weeks.
- Reweight what you optimize forLocal-first agents lean on the model's training data and cached indices far more than a cloud engine does, so long-form, well-linked, entity-consistent public pages earn more citations than freshly published thin SEO content that a local model has never actually seen in training.
- Publish for the machine, not only for GoogleSharpen the sources local models trained on: your Wikipedia page, LinkedIn Company Page, G2 profile, Crunchbase entry, and canonical About page. A polished landing page a local model has never seen is invisible on a private laptop, no matter how well it ranks on Google today.
- Assume more research is going invisibleIf your dashboard shows a citation dip this quarter, do not assume buyers stopped researching you. Some of that traffic simply moved onto devices no third-party observability tool can measure, and that measurement gap will only widen as more local models ship on consumer hardware over the coming quarters.
What to do this week
Run a spot check. Ask a colleague to look your company up inside Perplexity Portable Computer, ChatGPT desktop, and Claude side by side, and compare the three answers. Note where the local answer omits a fact the cloud answer includes. That omission usually points to a page a crawler indexed but the base model never saw. Rewrite it as a primary source: your own domain, your name, a clean publish date, and one specific claim. That is the format both retrievers and model training pipelines actually reward when they select a citation.