Both Tandem Browser and Comet (Perplexity's AI browser) are part of the wave of browsers that take AI seriously as a first-class participant rather than a sidebar. They make different choices about openness, which AI model you can use, and where your data lives. This page is a balanced look at where each fits.
| Tandem Browser | Comet | |
|---|---|---|
| License | MIT (open source) | Proprietary |
| Source available | Yes — full repo on GitHub | No |
| Where it runs | Your machine, local-first | Cloud-hosted features |
| Model choice | Bring your own (Claude, GPT, Gemini, OpenClaw, Ollama, LM Studio, custom) | Perplexity-managed |
| Works offline | Yes (with local model) | No — needs cloud |
| MCP support | Native — 250+ tools | No |
| Multi-agent | Yes — multiple agents in one browser | Single AI |
| Remote agents over Tailscale | Yes | N/A |
| UX polish | Developer preview — rough edges | Production-grade, refined |
| Install effort | Clone repo, npm install | Download installer |
| Support | Community via GitHub Discussions | Paid tiers with support |
| Price | Free | Free + paid subscription tiers |
Both reject the "AI sidebar bolted onto a normal browser" pattern. Both treat browsing as something an AI should be able to participate in directly, not just observe. The category is young and there's genuine room for multiple approaches — Comet's polished managed-product approach and Tandem Browser's open-source local-first approach are both legitimate answers to "how should browsers and AI work together."