Perplexity Computer adds Android support and local Comet browser control

• Perplexity expanded Computer from iOS to Android, making the agent available on both major mobile platforms, as Perplexity's Android launch confirmed and Wes Roth's recap echoed.
• The bigger implementation change is inside Comet: Perplexity says the Comet control post that Computer can now "take full control of Comet" and use a browser agent across sites and apps you’re already logged into.
• Perplexity is positioning that Comet flow as a way around per-site integrations, with the product post explicitly saying it works "without the need for connectors or MCPs" and a supporting breakdown from AlphaSignal's thread describing local cookie-based access.
• Early demos show one agent surface spanning phone and browser, and TestingCatalog's note adds that the Comet version can operate open tabs and reuse in-browser context.

Perplexity’s Android launch post is the clearest new surface-level update: “Computer is now on Android.” That follows the earlier iOS rollout and gives the company’s task-executing agent coverage across both mobile ecosystems, with a supporting reaction summarizing the footprint as iOS, Android, and Comet.

The more consequential release is Perplexity’s Comet control announcement, which says Computer can “take full control of Comet to complete tasks.” Perplexity describes it as a browser agent that can access “any site or logged-in app with your permission,” and says the feature is “available to all Computer users on Comet,” with access routed through the Comet page.

Perplexity’s own description says the agent works inside Comet “without the need for connectors or MCPs.” That matters because the browser session itself becomes the integration layer: instead of building API connectors for each SaaS app, the agent acts in the logged-in browser you already have.

A supporting walkthrough from AlphaSignal's thread makes the model more explicit: “your cookies stay on your machine,” the agent is “fully local,” and it can operate “any site you’re logged into.” Those are third-party claims, not a formal spec, but they line up with Perplexity’s first-party framing around permissioned access to logged-in apps. TestingCatalog also reports that the Comet version can operate open tabs and “seamlessly access necessary context,” which suggests session and tab state are part of the execution model.

Taken together, these launches turn Computer into a cross-surface agent: mobile for initiating tasks, and Comet for browser-native execution on authenticated web apps. The demo attached to the Comet post shows a browser flow that starts with “Ask Computer” and ends with “Flight booked successfully,” illustrating the intended handoff from natural-language request to UI-level completion.

The practical engineering angle is less about a new API than about a new control plane. Perplexity is betting that local browser control can remove a chunk of integration and auth setup that would otherwise require connectors, MCP servers, or custom glue code, while keeping the agent inside the user’s existing session context Perplexity announcement supporting thread.