Claude Projects vs Comet Browser by Perplexity AI

“The primitive here is a named, persistent system-prompt-plus-document-store scoped to a workspace — which is genuinely the thing developers have been duct-taping together with system prompt files committed to git and copy-pasted on every new chat. The DX bet is 'make the right thing the default thing': instead of building a wrapper that injects context programmatically, Anthropic just made the UI do it natively. The gap is API parity — if Projects context doesn't flow through the API with the same scoping, developers will still be hand-rolling this, and that's the specific thing I'd want confirmed before calling this a full ship.”

“The direct competitor is ChatGPT's Custom Instructions plus Memory, which has had persistent context for over a year — so Anthropic is catching up, not leading. The scenario where this breaks is team use at scale: shared document libraries with no versioning, no access controls beyond plan-level sharing, and no audit trail mean the first time a team's shared prompt gets silently edited and causes a bad output, trust collapses. What kills this in 12 months isn't a competitor — it's Anthropic itself shipping a proper API-native version that makes the UI feature redundant for the power users who care most about it.”

“The category is agentic browser automation — direct competitors are Anthropic's Computer Use, OpenAI Operator, and Arc's now-shelved Browse for Me, all of which have demonstrated the same core loop and hit the same walls: form auth, CAPTCHAs, and any site that detects non-human behavior. Comet breaks the moment a user wants it to handle a logged-in, dynamic SPA that rate-limits bots — which is most of the web that matters. What kills this in 12 months: OpenAI ships Operator to all ChatGPT users for free and Perplexity's differentiation collapses to brand preference. To earn a ship, Comet needs to demonstrate persistent session handling and a credible story for the 60% of high-value tasks that live behind auth walls.”

“The job-to-be-done is sharp and singular: stop re-explaining yourself to Claude every time you start a new conversation. Onboarding is as fast as it gets — create a project, paste your instructions, upload a doc, done, under two minutes to value. The product opinion baked in here is correct: most users don't need a memory graph or semantic search over past conversations, they need a stable persona and a document library, and Claude Projects makes exactly that bet without over-engineering it. The gap between shipped and needed is team permission controls — right now it's blunt-instrument sharing, and that will matter the moment any organization with more than five people tries to use this seriously.”

“The job-to-be-done as stated is 'complete multi-step web tasks autonomously' — that sentence contains an 'and' hiding inside 'multi-step,' which means this product is trying to solve task delegation, context retention, and web navigation simultaneously before nailing any one of them. The onboarding reality: users join a waitlist, get access inside a Pro subscription, and then face the blank-slate problem of not knowing which tasks are reliably automatable versus which will silently fail halfway through. That's not a 2-minute path to value — that's a discovery tax. The product isn't complete enough to replace any existing workflow today because there's no task library, no failure transparency, and no way to audit what the agent actually did. Until Comet ships a defined set of tasks it handles end-to-end with high reliability and surfaces that clearly at onboarding, it's a demo with a waitlist, not a product.”

“The thesis this bets on: within two years, AI assistants aren't used as one-off query tools but as persistent collaborators with institutional memory, and whoever owns the persistent context layer owns the workflow. The dependency that has to hold is that Claude remains the preferred model for knowledge-work tasks — if GPT-5 or Gemini Ultra pulls far enough ahead on capability, users don't move their Projects, they just stop opening the tab. The second-order effect nobody is talking about: shared Projects make Claude's system prompt a team artifact, which means prompt engineering starts being treated like documentation — owned, versioned, and argued about in PRs. That's a genuine shift in how organizations relate to AI, and Anthropic is positioning itself as the place where that institutional knowledge lives.”

“The thesis here is specific and falsifiable: by 2027, the browser tab is no longer a viewport you stare at — it's a task queue you delegate to. Comet is betting that the interface layer between humans and the web collapses from 'navigate and click' to 'state intent and verify result.' That's a real trajectory, and Perplexity is one of the few players with a live search index plus the intent-capture surface to make the delegation model feel natural rather than scripted. The second-order effect that matters: if Comet works, SEO as a discipline dies faster than anyone is modeling — the bot reads the page so the human doesn't, and click-through becomes irrelevant. The dependency that has to hold: users must be willing to hand over ambient browsing context to Perplexity's servers, which is a trust bet that sits on regulatory quicksand. Still, as a positioned bet on the trend of intent-first computing, this is early and credible rather than late and derivative.”

“The buyer is a Perplexity Pro subscriber who already pays $20/month — Comet is a retention and upgrade mechanism dressed as a product launch, which is actually smart distribution. The moat question is harder: browser distribution is a graveyard (ask Opera, Brave, Arc) and the switching cost of a browser is enormous for consumers but thin for Perplexity because users won't abandon Chrome for search features alone. The business survives model cost compression because Perplexity's value isn't the underlying LLM — it's the index and the task orchestration layer sitting on top of it. What worries me is the expand story: once you've automated the tasks a Pro user cares about, what's the upsell? There's no obvious enterprise tier with audit logs and admin controls mentioned at launch, which means the revenue ceiling is whatever the Pro subscriber count is. Viable, but not yet a standalone business thesis.”