Signal › Feed

OpenAI, Google, Anthropic, and Microsoft Back a Single AI Training Opt-Out Token — What Every Publisher Needs to Know Before February 2027

Perplexity launched Teammates on November 5, 2026 — persistent agents that run in isolated cloud environments, coordinate with each other, and own jobs from start to finish. Here's how they compare to Claude Duet and OpenAI Dots, and what the $200 pricing tier signals.


Perplexity processed 780 million queries a month on its way to a $20 billion valuation — and every one of those queries followed the same pattern: user asks, AI answers, session ends. On November 5, 2026, Perplexity changed that model. Teammates are persistent agents that take on jobs rather than answer questions, work through them in isolated cloud environments, and return with results rather than responses. The product is locked behind the $200-a-month Max plan, making it the most expensive entry point for any persistent agent capability currently offered by a major AI lab.

The question for every company evaluating Perplexity Teammates is not whether persistent agents are useful. The question is whether the specific way Perplexity has architected them — with isolated environments, multi-agent coordination, and a Max-only pricing wall — is the right foundation for the workflows you are trying to automate. This piece examines what Teammates actually does, how it compares to Claude Duet and OpenAI Dots, and what the $200 pricing tier signals about where the persistent agent market is heading.

What Perplexity's Teammates Actually Do

The fundamental difference between Teammates and a standard chatbot interaction is not intelligence — it is persistence and task ownership. When you give Teammates a job, it does not return a synthesized answer. It takes the job, figures out the steps required, coordinates with other agents if needed, and works through each step in a sandboxed cloud environment with its own desktop and browser. Completion can take hours. The agent sends updates as work progresses and flags decisions for human review when it hits something that requires judgment.

The architecture is built on top of Perplexity Computer, the company's autonomous browsing and execution layer that launched earlier in 2026. Each Teammate runs in its own isolated environment — meaning it cannot access data from other agents' sessions or from the user's local machine unless explicitly granted. That isolation design serves two functions: security containment and parallelism. You can run multiple Teammates simultaneously without risk of session pollution, and each can work on a different project without awareness of the others.

Teammates are designed around specific business functions. The marketed use cases include deep research projects that span multiple documents and sources, data analysis requiring sequential web lookups, QA testing workflows for software products, ticket triage and routing in support contexts, and marketing operations like prospect research and competitive monitoring. Each Teammate can be configured with its own role, skill set, and memory — it learns from past corrections and stores context across sessions.

The Slack integration is particularly notable. Teammates can monitor Slack channels, receive assignments through messages, and post status updates to specified channels without breaking out of their sandboxed environment. That design bridges the gap between the agent's isolated execution context and the human team's existing communication infrastructure — a problem that most agent platforms solve badly, by either requiring full tool integration or accepting that agents operate in a parallel context humans rarely check.

The Pricing Architecture: What $200 a Month Signals

Teammates is available exclusively to Perplexity Max subscribers. Max costs $200 a month or $2,000 a year. At that price point, it is the most expensive entry for any persistent agent capability currently offered by a major AI lab.

Compare the landscape as of November 2026:

PlatformPersistent Agent ProductMin Monthly PriceArchitecture
PerplexityTeammates$200 (Max plan)Cloud, isolated environments
OpenAIDots$100 (ChatGPT Pro)Cloud, approval-gated
AnthropicClaude Duet$20 (Pro plan)Cloud, proactive monitoring

That gap is significant. Claude Duet is included in the $20 Pro tier, making it accessible to nearly the entire Claude subscriber base. OpenAI's Dots requires ChatGPT Pro at $100, limiting it to the more committed subscriber segment. Perplexity's Teammates at $200 is not competing for the same user — it is making a deliberately higher-ticket product bet.

This matters because persistent agent products are still early enough that pricing is a category-formation signal as much as a revenue mechanism. The price tells the market what category the product lives in. At $20, Claude Duet lives in the personal productivity category. At $200, Perplexity Teammates is competing in a different set of mental budgets: B2B software, professional tools, and business workflow automation.

The credit model compounds this. During a promotional period, every Max plan includes free usage for Teammates; once that runs out, Teammates draw on the 10,000 monthly credits already bundled with Max. The business implication is that heavy agent use — the kind that runs research and QA projects for hours each day — will burn through credits quickly, pushing power users toward enterprise contracts with custom pricing and usage caps.

Claude Duet vs. Dots vs. Teammates: The Architectural Differences

All three products market themselves as persistent AI agents for work. The architectural differences are significant enough to affect which workflows they suit.

Anthropic's Claude Duet is the most proactive of the three. It monitors connected apps — email, calendar, documents, Slack — and surfaces work without being asked. The agent checks in periodically and proposes next steps based on what it has observed. The key design decision is push: Duet is designed to come to you rather than wait for you to assign it tasks. That design suits knowledge workers who want an AI layer over their existing communication tools, but it has a limitation: Duet operates across your existing apps through their permissions rather than in its own sandboxed environment.

OpenAI's Dots take the opposite approach on proactivity. Each Dot is a named, persistent version of the standard ChatGPT interface — a persistent context rather than an autonomous actor. Each Dot has its own name, instructions, memory, and tool access, but it waits for input rather than initiating. When consequential actions are required, it surfaces approval requests. The design suits users who want persistent context for a specialized role (a coding assistant, a research assistant, a writing partner) without autonomous operation.

Perplexity Teammates sits between them on the initiative spectrum. Teammates initiate against assigned tasks and work through them autonomously, like Duet's operational model — but they wait for assignments rather than proactively surfacing work, more like Dots. The key difference from both is multi-agent coordination: Teammates are explicitly designed to spawn and coordinate additional agents, which neither Duet nor Dots currently supports. That capability makes Teammates more suited for complex, multi-step workflows that require parallel work streams.

The isolation model is also distinct. Because each Teammate runs in a sandboxed cloud environment, users running agents for different clients or projects get stronger data separation than the shared-context models of Duet or Dots. For consultants, agencies, or teams working across multiple accounts, that separation is a material product difference.

The Activation and Retention Equation for Always-On Agents

The emergence of persistent agent products creates a fundamentally different activation and retention equation than traditional SaaS. Standard SaaS products are measured by activation (did the user perform the first value-generating action?) and retention (do they keep coming back?). Those metrics assume the product is passive — users come to it. Persistent agents invert this.

The activation problem for AI agents is not whether users try them. It is whether users successfully delegate work and trust the output. The hardest part of agent activation is not the first task — it is the second and third, after the user has seen the agent make decisions they would have made differently and had to decide whether to correct it or accept its judgment. Agents that cannot navigate that trust-building loop without exhausting user patience create high short-term activation but terrible retention.

This is the activation design challenge that all three persistent agent platforms are still solving. Mixpanel's research on AI agent analytics found that the highest-retention AI agent cohorts are those where the agent surfaces a decision for human review at the right frequency — not so often that it feels like a manual tool, not so rarely that the user loses confidence in its judgment. The calibration varies significantly by task type and user segment.

Perplexity Teammates' design bets that isolation and task-ownership are the right foundation for high retention in the enterprise segment. If the agent runs in its own environment and owns a defined job from start to finish, the user knows exactly what to expect from it and what to verify. The alternative — an agent that integrates deeply into existing tools and touches multiple data sources — creates broader capabilities but also broader failure modes that are harder to verify.

RevenueCat's data showing 79% annual churn for AI apps is the starkest quantification of the retention problem. Most AI products have strong activation and terrible long-term retention. The products that beat that curve are those that have found a workflow integration pattern that becomes genuinely load-bearing — where the user cannot easily imagine returning to the previous approach. Persistent agents with task ownership are a credible attempt to build that kind of dependency. The question is whether $200 a month is the right price to get users into the trial period long enough to build it.

Multi-Agent Coordination: The Capability That Separates Teammates

The most technically significant aspect of Teammates is multi-agent coordination. Perplexity confirmed at launch that multiple Teammates can be deployed simultaneously and that they can coordinate with each other — passing work between agents, spawning sub-agents for specific tasks, and aggregating results.

This capability is architecturally new among the persistent agent tier from major consumer AI labs. Claude Duet and OpenAI Dots are fundamentally single-agent designs — each user gets one persistent assistant. Teammates explicitly supports parallel deployment of multiple specialized agents working in concert.

The business implications are substantial. A single Teammate can conduct primary research on a prospect. A second can analyze financial filings and news coverage simultaneously. A third can begin compiling results as the other two complete. That parallel architecture collapses the wall-clock time for multi-part research workflows from hours to something closer to the time of the longest single step.

For enterprise teams that run regular research or analysis workflows at volume — competitive intelligence, due diligence, customer research — the parallelism compounds into a substantial operational advantage over sequential approaches. The question is whether the current Max credit model prices those workflows economically, or whether enterprise contracts with custom pricing and usage caps are required for teams doing real volume.

The architectural choice also reflects a different competitive positioning than Anthropic and OpenAI. Both companies have enterprise multi-agent frameworks — Anthropic's MAS architecture and OpenAI's Swarm — but neither exposes multi-agent coordination as a consumer-facing persistent agent feature. Perplexity is betting that bringing multi-agent coordination to the individual subscriber level, rather than requiring enterprise API access, creates a retention moat among power users who would otherwise cap out on what a single agent can do.

The Competitive Reality: What Perplexity Is Actually Competing Against

Perplexity Teammates competes on two dimensions simultaneously: against Claude Duet and OpenAI Dots for persistent agent mindshare, and against workflow automation platforms like Zapier and Make for the enterprise workflow automation budget.

The first competition is about product category formation. The lab that defines what a persistent AI agent should do — the right balance of autonomy and oversight, the right integration model, the right task types — will have a durable product advantage in a category that does not yet have established norms. Perplexity's bet on task-ownership and isolation is a specific hypothesis about what enterprise users will find reliable enough to trust with real workflows.

The second competition is about replacing existing software purchases. Workflow automation platforms represent a substantial enterprise budget line. The economic case for replacing a Zapier workflow or a Make automation with a Teammates-based approach requires demonstrating that the agent handles exception cases better (automation tools break on edge cases), adapts to changing data structures without reconfiguration, and costs less per workflow than the existing tooling plus human supervision.

The $200 price point is expensive relative to Zapier's business tiers but cheap relative to the full cost of a human analyst doing the same research or QA work. That positioning — premium compared to automation software, economical compared to headcount — is the target market frame. It is a viable frame if Teammates can consistently deliver research or QA work that would have taken a human two to four hours in under 30 minutes of wall-clock time. The enterprise pricing model and enterprise deployment path are the two gaps that need to close before that positioning becomes broadly testable at scale.

Perplexity's Strategic Position in the Persistent Agent Race

Perplexity's growth to $200M ARR without a paid acquisition budget rested on distribution deals, product-led growth through shareable outputs, and a reputation for high-quality research answers. Teammates extends all three of those mechanics. It gives enterprise users a reason to anchor on the Max subscription rather than treating Perplexity as a research tool. It creates outputs — research briefs, QA reports, analysis documents — that are shareable and serve as distribution vectors. And it leverages the existing Perplexity brand association with high-quality, cited research.

The strategic risk is timing. Anthropic and OpenAI have significantly larger enterprise install bases through their existing Pro and Business subscribers. If those platforms iterate their persistent agent products faster than Perplexity can build enterprise trust in Teammates, the first-mover advantage in the persistent agent category — which Perplexity currently does not hold, since Claude Duet launched in October 2026 — becomes harder to overcome.

The iOS and desktop app gap is an immediate limitation. Persistent agents that only run on web create an asymmetric use case: they are most useful for work that happens across multiple devices and contexts, but users can only manage them from a browser. Mobile and desktop apps are on the roadmap but not yet shipped, which limits Teammates' utility for the mobile-first workflows that represent an increasing share of enterprise knowledge work.

The Questions Every Buyer Should Ask Before Committing to Teammates

For enterprise teams evaluating whether to build workflows around Perplexity Teammates, the deployment decision turns on five practical questions.

1. What is the agent's data access boundary? Teammates run in isolated cloud environments, which limits their access to data you explicitly provide. If your workflow requires real-time access to internal databases, CRM data, or private document stores, understand the integration model before assuming the agent can reach those sources.

2. Can you verify the agent's output reliably? Teammates are designed to surface decisions and return results. The effectiveness of human oversight depends on whether you can verify the outputs without re-doing the work. Research briefs are verifiable. Code changes are verifiable with tests. Financial models require more careful audit. Match the task type to the verifiability ceiling you can tolerate.

3. What happens when the agent fails mid-task? Persistent agents that work for hours can fail partway through a complex workflow. Understand the error handling model: does the agent report the failure point, preserve completed work, and allow retry from a checkpoint, or does a failure require restarting the full workflow?

4. How does credit consumption map to your workflow volume? The 10,000 monthly credit bundle sounds large until you model the credit cost of a typical research workflow. Get the per-step credit cost from Perplexity's documentation and model your volume before committing to Max subscriptions at scale.

5. What is the enterprise pricing model? Perplexity has not published enterprise pricing for Teammates. For teams deploying multiple agents across multiple projects, the per-seat Max model may not be the right economic structure. Engage the enterprise sales team before building workflows that depend on pricing stability.

What Comes Next

Perplexity Teammates launched as a web-only product, with iOS and desktop support planned but not yet shipped. Enterprise pricing for teams deploying at scale has not been published. The credit cost for complex workflows at real enterprise volume is not yet documented. These gaps are typical for an early-stage product launch and will be resolved — but they mean that production deployments at scale should wait for the enterprise tier.

The right near-term action for most enterprise teams is to run a pilot on the Max personal subscription with one or two workflows that have clear success criteria and verifiable outputs. That pilot costs $200 to $400 for two months of learning — enough to establish whether Teammates handles your specific task types with the reliability you need before committing to enterprise contracts.

The team pricing and mobile app timelines are the most important signals to watch. When Perplexity publishes enterprise pricing and ships mobile and desktop apps, the activation friction and pricing uncertainty that currently limit Teammates' enterprise adoption will largely resolve. Teams that have run pilots and built confidence in the product's handling of their specific workflows will be positioned to move quickly. Teams that wait for the enterprise tier to stabilize before evaluating will be starting six to nine months behind.

Takeaway: Perplexity Teammates is the most capable persistent agent in its class for multi-step research and QA workflows, with a unique multi-agent coordination model that neither Claude Duet nor OpenAI Dots currently matches. The $200/month Max pricing is not a barrier for enterprise teams running work that would otherwise cost $500 to $1,000 in analyst time per month — but it is a commitment that requires a credible pilot plan before production deployment. The enterprise pricing model and mobile support are the two gaps that need to close before Teammates can claim the enterprise workflow category.

Frequently Asked Questions

What are Perplexity Teammates and how do they work?

Perplexity Teammates are persistent AI agents that take on jobs rather than answer single questions. Each Teammate runs in an isolated cloud environment — its own sandboxed desktop and browser — and works through a task from start to finish, coordinating with other agents when needed, surfacing decisions for human review, and returning completed results rather than synthesized answers. They are built on top of Perplexity Computer, the company's autonomous browsing and execution layer. Teammates remember past sessions, learn from corrections, and can monitor Slack channels to receive assignments and post status updates. Access is limited to Perplexity Max subscribers at $200 per month. The key architectural distinction from Claude Duet and OpenAI Dots is multi-agent coordination: multiple Teammates can run simultaneously and pass work between each other, enabling parallel execution of complex multi-step workflows.

How do Perplexity Teammates compare to Claude Duet and OpenAI Dots?

All three are persistent AI agent products from major AI labs, but their architectures reflect different hypotheses about what enterprise users need. Anthropic's Claude Duet is proactive — it monitors connected apps and surfaces work without being asked, with periodic check-ins across email, calendar, and documents. It operates across your existing app integrations rather than in an isolated environment. OpenAI's Dots are more like named, persistent chatbot contexts — specialized assistants with their own memory and tool access that wait for input rather than initiating. Perplexity Teammates sit between them: they initiate against assigned tasks and work autonomously like Duet, but wait for assignments rather than proactively surfacing work like Dots. The unique capability is multi-agent coordination — Teammates can spawn and coordinate parallel agents in a way that neither Duet nor Dots currently supports. On pricing, Duet is included in the $20 Pro tier, Dots requires the $100 ChatGPT Pro plan, and Teammates requires the $200 Max plan — the most expensive entry in the category.

What tasks are Perplexity Teammates best suited for?

Teammates are designed for tasks that require multiple sequential steps, real-time web research, and verifiable outputs — not for open-ended conversations or creative work. The marketed use cases include deep research projects across multiple documents and sources, competitive intelligence workflows that require parallel data gathering, QA testing for software products, ticket triage and routing in customer support environments, and prospect research for sales teams. The isolation model — each agent runs in its own sandboxed environment — makes Teammates well suited for tasks that require strong data separation between projects or clients, such as consulting work across multiple accounts. The multi-agent coordination model makes them suited for workflows where parallel execution would substantially compress wall-clock time, such as research projects with multiple independent components. They are less suited for tasks that require deep integration with internal databases or private document stores without explicit integration configuration.

How does the Perplexity Teammates credit model work?

During the initial launch period, Max subscribers receive a free allocation of Teammates usage on top of the standard Max plan. Once that promotional allocation is exhausted, Teammates usage draws on the 10,000 monthly credits bundled with the Max subscription. Credits are consumed per operation — research steps, tool calls, and agent actions each cost credits at rates that vary by task complexity. For light users running occasional research tasks, the monthly credit bundle is likely sufficient. For teams running agents on daily workflows, the credit bundle may be exhausted before month end, pushing usage toward enterprise contracts with custom pricing. Perplexity has not yet published a detailed credit cost schedule, so teams planning production deployments should request that information directly before committing to Max subscriptions at scale.

Is Perplexity Teammates available to enterprise customers?

At launch, Teammates is available to individual Perplexity Max subscribers through the web interface. iOS and desktop apps are planned but not yet shipped. Enterprise pricing for teams deploying multiple Teammates across multiple projects has not been published. Some sources indicate that Enterprise Pro and Enterprise Max organization accounts were not automatically included in the initial rollout. For enterprise teams evaluating Teammates for production deployment, the most reliable approach is to run a pilot on Max personal subscriptions with well-defined workflows, then engage Perplexity's enterprise sales team for contract pricing before scaling. Building production workflows on individual Max subscriptions at $200 per user creates a pricing and support structure that is unlikely to hold at enterprise scale.

What is the activation and retention risk for persistent AI agent products?

The activation and retention dynamics for persistent agents are fundamentally different from standard SaaS. The hardest part of agent activation is not the first task — it is the second and third, after users have seen the agent make decisions they would have made differently and had to decide whether to correct it or accept its judgment. Agents that cannot navigate that trust-building loop without exhausting user patience create high short-term activation but poor long-term retention. RevenueCat's data showing 79% annual churn for AI apps reflects this dynamic. The products that beat that churn curve are those that find a workflow integration pattern that becomes genuinely load-bearing — where users cannot easily imagine returning to the previous approach. Persistent agents with clear task-ownership and verifiable outputs are a credible attempt to build that kind of dependency, but the trust-building period requires careful workflow selection. Starting with tasks that have clear success criteria and verifiable outputs — research briefs, QA reports — is the right approach before moving to tasks where verification requires as much effort as the task itself.