Droid vs Perplexity
Comet acts in your browser. A droid acts when you're not there.
Perplexity is the tool most people reach for when they want an answer with its sources attached, and Comet has moved it well past search into doing things in the tab. It only works while you're sitting there, though. A droid runs on its own, in your channels, on a schedule, with approval gates on anything that touches the real world.
- Runs with the laptop closed
- Lives in Slack, email & phone
- Governed write actions
- Shared across the team
The honest short version.
Perplexity is excellent at what it does. Sourced answers, Deep Research, and now Comet, an AI-native browser where the assistant holds context across every tab in a Space and will summarise, draft and buy things for you. Connectors reach into Gmail, Drive, Notion and the rest so it can search your own material alongside the web. All of it happens in a session you're present for. A droid is the other half: it works unattended, reaches people on Slack and SMS and the phone, and writes to your systems under per-tool policies rather than reading from them.
Droid and Perplexity, line by line.
The same job, two tools. Here's how they differ where it actually counts.
| Capability | Droid | Perplexity |
|---|---|---|
| What it is | An AI worker you hire for a role. It joins calls, works your apps, and finishes deliverables. | An answer engine with an AI browser attached, built around research you can check. |
| Where it lives | In Slack, Teams, email, SMS and on a real phone number, which are the surfaces your team already uses. | In the Perplexity apps and the Comet browser, plus Samsung Internet on Android. |
| Research quality | Researches as part of doing a job, and cites what it used. This isn't where a droid claims an edge. | Best in class. Deep Research, Model Council and inline citations are the reason people pay for it. |
| Taking action | Managed OAuth to ~3,000 apps with read / write / destructive actions and per-tool policies. | Comet acts inside the browser session: sends an email, fills a form, completes a purchase. |
| Your own data | Typed memory plus governed connections it can both read and write. | Connectors for Gmail, Calendar, Drive, Notion, SharePoint, OneDrive and Box. Read and search, mostly. |
| Unattended work | Durable scheduled and event-triggered runs, with your laptop closed. | You drive it. Close the browser and nothing continues. |
| Voice, phone & video | Live voice calls, its own phone number, and it joins Zoom / Meet / Teams with screen-share. | Voice input in the apps. No phone number, and it doesn't join meetings. |
| Team & sharing | One workspace, shared memory and automations across everyone. | Spaces can be shared, and Enterprise adds org file search. The assistant itself is per-seat. |
| Approvals & governance | Sensitive actions wait for approval, and credentials sit in a vault the model never sees. | Enterprise controls over data and access, but no per-action gate on what the browser agent does. |
| Pricing shape | Workspace credits, shared across the whole team. No per-seat charge. | Per-seat (Pro / Max / Enterprise Pro / Enterprise Max), with connectors gated by tier. |
Some of these rows go the other way, and they stay in. A comparison page where the competitor never wins is an advert, and readers can tell.
What a droid adds.
Comet covers the browser well. These are the parts of a job that happen somewhere else.
Works while you're asleep
Durable scheduled and event-triggered runs, so the Monday reconciliation happens without anyone opening a tab.
Writes, not only reads
Connectors that search your Drive are useful. A droid updates the CRM, files the record and sends the mail, under per-tool policies.
Reaches people
Slack, Teams, email, SMS and a phone number, so colleagues and customers can reach the worker rather than the operator.
Joins the call
Live voice and video with screen-share, taking actions during the meeting instead of researching it afterwards.
Shared, not per-seat
One workspace the whole team @mentions, with memory that carries between people rather than living in your session.
Gates the risky bits
Anything with a side effect waits for approval, and credentials live in a vault the model never sees.
Where Perplexity shines.
When the job is "find out and show me where that came from", this is the best thing available.
- Sourced answers with inline citations, which is still the most trustworthy shape for research.
- Deep Research does hours of reading and comes back with something you can actually check.
- Comet's Spaces hold context across every tab in a session, so it understands the whole thread of what you're doing.
- Connectors let it search your Drive, inbox and Notion next to the open web in one query.
- If you want an answer rather than a worker, nothing here beats it on speed or sourcing.
The questions that come up most.
Comet acts inside the browser you're driving, which is genuinely useful and quite fast for one-off jobs. A droid acts through governed OAuth against APIs, so the action is scoped per tool, gated for approval when it has a side effect, logged, and repeatable on a schedule with nobody watching. Different mechanism, and it shows up most when the same job has to happen every week.
Perplexity, for pure research, without much argument. A droid researches in service of finishing a task, so if what you want is the answer and the sources, use the tool built for it.
Yes, including sites with no API, and it can read and act on a page. Browsing is the fallback rather than the main path, though. Where an API exists, going through governed OAuth is faster and far easier to control.
Both do. The connection is shaped differently: Perplexity's connectors are built to search across your material and the web together, whereas a droid's are built to take action in those systems, which is why they carry per-tool scopes and approval gates.
No. Your conversations, files, and integration data aren't used to train shared models. Droid's providers operate under no-training, zero-retention terms for Droid traffic. See /security for the full posture.
For the part that happens after the answer.
Starter credits, no card. Keep Perplexity for the research and hand a droid the job that has to happen every week whether or not you're at your desk.