Comet

Overview

Comet is a standalone AI browser from Perplexity built to let an AI agent interact directly with the web and execute browser-based tasks reliably. In newsletter coverage, Comet is positioned as a practical alternative when traditional integrations such as connectors or MCP-based workflows are unavailable, insufficient, or too brittle for the job. It also appears to function as a local browser tool for Computer, enabling end-to-end task completion inside a real browsing environment.

For AI Product Managers, Comet matters because it represents a product pattern that is becoming increasingly important: giving agents a controlled browser runtime instead of relying only on APIs and app integrations. That expands the range of automatable workflows, but it also raises important questions around security, deployment, governance, and model choice. Comet’s enterprise positioning, MDM deployability, CrowdStrike Falcon integration, and granular agent controls make it especially relevant for PMs evaluating how to operationalize autonomous web actions safely at scale.

Key Developments

• 2026-01-22 — Aravind Srinivas announced that Comet’s browser agent would default to Opus 4.5 for Max subscribers, signaling a focus on stronger default model performance for browser-based AI assistance.
• 2026-03-17 — Aravind Srinivas said Computer could use the local browser Comet as a tool, enabling it to perform tasks without relying on connectors or MCPs; this was framed as a meaningful product advantage.
• 2026-03-18 — Comet was described as an enterprise AI browser deployable to thousands of devices via MDM, with integration into CrowdStrike Falcon for suspicious link and file detection, plus granular controls over what agents can do and where they can operate.
• 2026-05-08 — Comet was noted as launched as a standalone browser, designed to let the Personal Computer AI execute web-based tasks reliably when conventional connectors fall short.

Relevance to AI PMs

• Designing around connector gaps: Comet shows how browser-native execution can extend agent coverage to workflows that lack stable APIs or supported integrations. PMs can use this pattern to prioritize automation opportunities beyond the connector ecosystem.
• Planning enterprise-safe agent deployment: The MDM deployment model, security integrations, and permission controls highlight the operational requirements for shipping agentic tools into real organizations. PMs should treat governance, endpoint deployment, and action boundaries as first-class product requirements.
• Choosing the right execution layer: Comet illustrates a tactical tradeoff between API-based automation and browser-based automation. PMs can use this distinction to decide when reliability, compatibility, or reach justify a browser agent despite added complexity.

Related

• Perplexity — The company behind Comet, framing it as part of its broader AI assistant and agent product strategy.
• Aravind Srinivas — Publicly announced multiple Comet updates, including enterprise deployment, model defaults, and integration with other tools.
• Computer — Uses Comet as a local browser tool, suggesting Comet acts as an execution environment for web tasks.
• CrowdStrike Falcon — Integrated with Comet to detect suspicious links and files, reinforcing Comet’s enterprise security posture.
• Opus 4.5 — Set as the default browser-agent model for Comet in one announcement, indicating model selection is part of the product experience.