Comet

Overview

Comet is an AI browser and browser-agent product associated with Aravind Srinivas, positioned as both an end-user browsing environment and an execution layer for AI agents. Across the newsletter mentions, Comet appears in three important product frames: as a browser agent with a configurable default model for subscriber sessions, as a local browser tool that another agent system (Computer) can operate directly, and as an enterprise browser deployable at scale with security integrations and policy controls.

For AI Product Managers, Comet is a useful case study in how product defaults, tool access, and enterprise controls shape user experience and product strategy. Its switch to Opus 4.5 as the default model for Max subscribers highlights how model-routing decisions can materially affect perceived quality, speed, and consistency. Its enterprise launch, including MDM deployment, CrowdStrike Falcon integration, and granular agent permissions, also shows how browser-native AI products are evolving from consumer demos into managed, secure enterprise surfaces.

Key Developments

• 2026-01-22 — Comet adopted Opus 4.5 as the default model for the browser agent for Max subscribers, underscoring the importance of default model selection in subscriber experience and product positioning.
• 2026-03-17 — Aravind Srinivas announced that Computer could use the local browser Comet as a tool, enabling task execution without connectors or MCPs; this positioned Comet as a direct action surface for agent workflows.
• 2026-03-18 — Comet was launched as an enterprise AI browser deployable to thousands of devices via MDM, integrated with CrowdStrike Falcon for suspicious link and file detection, and equipped with granular controls over what agents can do and where they can operate.

Relevance to AI PMs

1. Model defaults are a product decision, not just an infra decision. Comet’s defaulting to Opus 4.5 for a subscriber tier illustrates how PMs should think about model choice as part of the core UX: response quality, latency, cost, and user trust are all affected by the default path.

2. Browser-native agent execution can reduce integration overhead. The fact that Computer can use Comet directly suggests a product pattern where the browser itself becomes the universal tool surface. PMs can evaluate when direct UI-level action is preferable to building and maintaining many connectors or MCP-based integrations.

3. Enterprise adoption depends on security and governance primitives. Comet’s MDM deployment, CrowdStrike Falcon integration, and granular agent controls show the checklist PMs need for enterprise AI products: scalable rollout, observability, policy boundaries, and risk mitigation around links, files, and agent actions.

Related

• aravind-srinivas — Central figure behind the announcements and launch of Comet; his posts frame Comet’s positioning across consumer, agentic, and enterprise use cases.
• computer — An AI system/tool that can use Comet as a local browser tool, making Comet part of a broader agent execution stack.
• opus-45 — The model selected as Comet’s default for Max subscriber browser-agent sessions, making it relevant to discussions of model routing and product defaults.
• crowdstrike-falcon — Security platform integrated with Comet for suspicious link and file detection in enterprise deployments, highlighting the product’s enterprise-readiness and governance posture.