Perplexity introduced Teammates in a launch post dated November 4, 2026, giving users agents that can own ongoing work inside Perplexity Computer. The announcement focuses on continuity: maintaining a project’s context, noticing changes, and bringing results back for review.
Work continues across individual tasks
Perplexity says a teammate coordinates Computer sessions and other teammates, retaining project goals, previous work, shared files, and feedback. It can monitor a workstream and act when something changes instead of waiting for another question. Initial availability is on the web for Max subscribers.
The company also describes collaboration through Slack and handoffs between teammates. Existing Computer tools and Project permissions remain the access boundary. Each teammate has a separate environment and browser sessions; users can inspect progress, redirect the work, or take over its desktop.
A persistent thread changes supervision
The product page describes one continuing thread for each teammate. That can make an extended assignment easier to follow than a collection of unrelated sessions, provided the record distinguishes plans, attempted actions, completed work, and decisions awaiting the user.
Our analysis is that persistence creates a higher standard for staying aligned with the current request. Remembering a goal is useful only when an agent also recognizes that its owner changed the deadline, withdrew access, or replaced an earlier preference. A system that continues confidently with an obsolete instruction can create more work than it saves.
Evaluate a real recurring responsibility
A useful pilot would assign a bounded monitoring task with a clear result. For example, ask for a weekly review of an approved set of public product pages. Define what counts as a meaningful change, where the summary belongs, and which actions require a decision.
Then change one requirement during the pilot and check that the agent applies it on the next cycle. Interrupt an execution and inspect whether it resumes from verified state. Review whether a claimed completion links to the actual artifact, rather than only a plausible progress message.
Collaboration needs its own test. When one teammate hands work to another, the receiving agent should have enough evidence to inspect the result and enough context to understand the remaining objective. Several agents repeating the same assumption is not independent verification.
Access and outcomes remain separate
A connected service provides the ability to perform work; the user’s assignment determines what work is authorized. Teams should review those boundaries before allowing proactive changes or external messages. The meaningful adoption measure is verified progress with an understandable review burden, not the number of tasks started.
Teammates is a substantial step in Perplexity’s product direction because it puts ongoing responsibility above the individual prompt. Its practical value will depend on reliable follow-through, current context, and clear user control as the work evolves.