Glean Agents Platform vs Perplexity Comet

“The direct competitors here are ServiceNow's Now Assist, Microsoft Copilot Studio, and Salesforce Agentforce — all of which have massive distribution advantages. Where Glean actually earns its place is the knowledge layer: if you've already got Glean indexing your company's internal content with real permissions, building agents on top of that foundation is meaningfully different from a blank-slate agent builder. The scenario where this breaks is large enterprises with fragmented IT budgets, where Glean has to compete against the existing Microsoft 365 or ServiceNow contract rather than supplement it. What kills this in 12 months isn't a competitor — it's Microsoft bundling Copilot Studio capabilities deeper into M365 E5 licenses and making the 'we already have Glean' argument harder to close.”

“Comet is competing directly with Arc's Browse, Google's Project Jarvis, and Anthropic's computer-use demos — except those shipped broadly and Comet is invite-only for a Q3 2026 general rollout. The specific failure scenario is obvious: any task requiring login state management, CAPTCHAs, or multi-domain auth handoffs falls apart immediately, and Perplexity hasn't shown evidence of solving those problems at scale. My prediction for what kills this in 12 months: Google ships Gemini-native browser automation in Chrome, erasing Comet's differentiation with zero distribution disadvantage. To earn a ship, Comet needs to demo booking a multi-leg international flight with seat selection, payment, and confirmation — live, unscripted, first try.”

“The buyer here is the CIO or VP of IT, pulling from digital transformation or enterprise AI budget — not a departmental line item. Glean's smart move is that the Agents Platform is an expansion motion inside an existing Glean contract, not a net-new sale, which is the only land-and-expand story that actually works. The moat is real but narrow: it's the indexed, permissioned knowledge graph that takes months to build and tune per enterprise, creating genuine switching costs. The stress test is whether enterprises will consolidate on one platform player — if Microsoft or Salesforce offers 80% of this functionality bundled into existing spend, Glean's standalone value proposition compresses fast unless they keep the knowledge indexing quality visibly ahead.”

“The buyer here is the $20/mo Perplexity Pro subscriber, which means Comet is a retention feature masquerading as a product launch — there's no incremental revenue attached to it unless Perplexity spins it into a higher tier. The moat question is brutal: Comet's agentic capability sits on top of browser automation infrastructure that Google, Microsoft, and OpenAI are all building simultaneously, and none of them need to charge $20/mo to distribute it. The specific business problem is that Perplexity is spending engineering capital on a browser at exactly the moment when its search revenue model remains unproven — this is a distraction bet that only makes sense if it dramatically increases Pro retention or unlocks enterprise contracts. What would need to change: a dedicated Comet tier at $40-50/mo with verifiable task-completion SLAs and an enterprise sales motion.”

“The primitive here is a hosted agent runtime that uses Glean's search index as a retrieval layer and exposes workflow triggers — essentially a RAG-grounded agent builder with pre-built connectors. The DX bet is that enterprises want a no-code/low-code surface rather than composable APIs they can wire into their own stack, which is probably the right call for the buyer but makes this nearly useless if you want to integrate it into an existing internal toolchain. The moment of truth — can a developer get an agent running against real company data in under 30 minutes — is entirely gated behind the sales cycle and enterprise provisioning, which means there's no public hello-world to evaluate. The blog post has no repo, no public API docs, no sandbox, and no pricing: three red flags for any tool claiming to serve builders.”

“The job-to-be-done is precise: 'help enterprise employees get answers and trigger actions using company knowledge without requiring IT to build custom integrations from scratch.' That's a real, well-scoped problem. The completeness question is where Glean has an edge over blank-slate agent builders — because the knowledge indexing is already done for existing Glean customers, the activation cost for the first useful agent should be low compared to starting from Copilot Studio with an empty SharePoint. The gap I'd flag is that 'over 100 business apps' is a connector count, not a measure of integration depth — the real test is whether an agent can reliably take action in Salesforce or ServiceNow, not just read from them, and nothing in the GA announcement quantifies that reliability at scale.”

“The job-to-be-done is sharp: complete a web task I would otherwise do manually across 4-8 browser tabs. That's a real, recurring job with measurable time cost, and Comet is one of the first products to attempt it at the browser layer rather than the script or extension layer. The onboarding concern is real though — invite-only access means the vast majority of Pro subscribers can't evaluate whether this replaces their current workflow, making it impossible to call this a complete product today. The opinion baked into Comet is correct: the browser should understand goals, not just URLs. The gap between what's shipped and what's needed is a public availability date that isn't six months away, and documented task success rates so users can set realistic expectations before switching.”

“The thesis here is falsifiable and specific: by 2028, the browser is not a viewport but an execution environment, and the team that controls the AI-browser layer controls the intent graph of the web. Comet is betting on this at the infrastructure level — not bolting agents onto a tab, but rebuilding the browser around the agent primitive. The second-order effect that matters most is what this does to web analytics and SEO: if agents complete tasks without humans seeing pages, the entire attention economy built on pageviews collapses. Comet is riding the computer-use trend line and is roughly on time — OpenAI Operator launched earlier, but browser-native execution versus API-layer automation is a real architectural distinction worth watching. The dependency that has to hold: agentic task completion rates must cross ~85% reliability before mainstream users tolerate it.”