Comet Browser by Perplexity AI vs Rowboat

“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 'knowledge graph from email' promise is where these tools historically fall apart — noisy inboxes produce noisy graphs. And 'local-first' often means 'labor-intensive setup.' The abstraction is right but execution on messy real-world data is hard. Watch the 1-month reviews.”

“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.”

“Personal knowledge infrastructure that you own is becoming the moat in AI-augmented work. Rowboat's transparent, portable approach builds durable value. In two years the question won't be which AI assistant you use, but which knowledge graph underlies it.”

“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.”

“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.”

“Plain-text persistence + MCP + local model support is the right architecture. It'll survive AI winters and API deprecations. The Obsidian compatibility alone is a killer feature for the PKM crowd that already lives in that ecosystem.”

“Drafting meeting briefs and decks from accumulated context is the workflow I've wanted for years. The Obsidian integration means my notes and my AI context stay in sync naturally — no separate import/export dance.”