Perplexity Comet vs Stet

“The direct competitors here are Arc with Browse, Dia, and honestly just Operator from OpenAI — which already does agentic browser automation and has the distribution advantage of the most-used AI brand in the world. Comet's specific failure scenario: any workflow that requires logging into accounts with 2FA, handling CAPTCHAs, or navigating SPAs with dynamic state — which is most of the interesting automation targets. My 12-month prediction is that OpenAI or Google ships 80% of this natively into their existing browsers and Perplexity's differentiation collapses to 'we also have a search box.' To earn a ship, Comet needs to demonstrate agent reliability rates on real-world tasks above 80%, not cherry-picked demos.”

“The 'sounds like you' promise needs a lot of data to actually deliver — your voice profile is only as good as the writing samples it's trained on, and most people don't have a consistent, large corpus of their own writing. For casual dictators, this might just be Whisper with extra steps. Apple's built-in dictation is free and surprisingly good now.”

“The thesis here is falsifiable: by 2028, the browser becomes the agent runtime rather than a document viewer, and the team that owns the browser layer owns the automation stack. The dependency is that OS-level agent APIs from Apple and Microsoft don't make the browser layer irrelevant before Comet builds distribution. The second-order effect nobody's talking about is that if this works, Perplexity gains clickstream data on user intent that no search engine currently has — not just queries but the full task graph, which is a training data moat. They're riding the trend of intent-layer consolidation and they're early enough that the category isn't defined yet, which is the right time to plant a flag.”

“Voice-first computing is coming back, and the arms race for authentic AI writing assistance is heating up. The distinguishing factor won't be transcription accuracy — everyone has solved that — it will be voice fidelity. Stet is building in the right direction: local processing plus personal style models. Expect this architecture to be standard in two years.”

“The primitive is: a Chromium fork with an injected agent that can read and manipulate the DOM plus call Perplexity's inference API. The DX bet is that bundling the runtime into the browser eliminates the permission and injection problems that plague extension-based agents — that's actually the right call architecturally. But the moment of truth is trying to automate something that matters to you specifically, and without a published automation scripting interface, a local action log, or any developer surface to inspect what the agent is actually doing, this is a black box. The weekend alternative for a competent engineer is Playwright with a function-calling loop, which gives you full observability. Until Comet ships an agent trace viewer or a scripting API, it's a consumer demo, not infrastructure.”

“Open-source, local-first transcription with BYOK is the right architecture. I've been burned by voice tools that upload my audio to servers I can't audit. The voice profile approach for preserving style is technically interesting — I want to see how it handles domain-specific jargon and code-switching between formal and casual registers.”

“The buyer here is the Perplexity Pro subscriber who already trusts the brand with search — this is a land-and-expand move and the expand story is actually credible because browser replacement has natural stickiness once your bookmarks and session history are in. The pricing is smart: Comet ships included with Pro, which lowers the adoption friction to zero and lets Perplexity study task completion data before charging for the feature separately. The moat question is real though — the switching cost of a browser is high but Perplexity doesn't own an OS, a mobile platform, or an enterprise SSO, so enterprise expansion is a hard road. The business survives model commoditization because the value is in the task graph and user behavior data, not the inference itself.”

“This is genuinely exciting for writers and content creators. The homogenization of AI-assisted writing is a real aesthetic problem — everything starts sounding like the same LinkedIn post. A tool that actively fights that tendency by learning your specific voice is solving the right problem. Even if the voice model needs work, the direction is exactly right.”