Perplexity announced Teammates on 5 November 2026 and began rolling them out to Max users on the web. The dated announcement is preserved in this embedded CEO post; we could not retrieve X directly.
The product page describes agents that retain ongoing responsibilities, use existing Computer context, collaborate and follow up through Slack. Native mobile and desktop apps are still forthcoming. Treat the demonstrations as the vendor’s examples, not measured reliability.
Check eligibility before connecting work
The setup guide calls this a research preview for individual Max, not Pro. Enterprise Pro and Enterprise Max are excluded by default; ask your administrator. Behavior may change.
Perplexity says existing plugin and Project permissions apply, with separate computers, browsers and cookies per teammate. Saved credentials are encrypted and hidden from the agent. Shared chats are read-only for others, while people can interact in monitored Slack channels.
For an operator, the first decision is which work may leave the organization’s existing systems. A sandbox does not decide that policy. Review the data categories, permitted recipients, retention terms and actual connection permissions before handing over confidential material. Do not infer enterprise approval from an individual subscription.
Budget for the continuing job
The product page advertises temporary free Teammates usage, then consumption of Max’s included credits. It gives no promotional end date. Max pricing lists US$200 monthly or US$2,000 annually, with annual billing on the web.
The credit guide lists 10,000 monthly Consumer Max credits. Auto-refill is off by default. When credits run out, work pauses and can resume when credits return. Parallel agents, large inputs and frequent automations can raise usage, according to the Teammates guide.
A bounded first assignment
Our suggested pilot is deliberately smaller than the launch demonstrations:
- Choose one low-risk workflow, such as preparing a weekly report from approved, non-sensitive issue data. Name the person who checks the result.
- Write separate rules for reading, drafting, sending and changing records. Specify the destination and which actions require human approval.
- Use a small acceptance set containing an ordinary case, an ambiguous request and an unavailable source. Ask for evidence of completed work, not just a confident status message.
- Review task history and actual usage after the first run. Set a stop condition and a review date before allowing a recurring assignment to continue.
These are proposed operating checks, not our test results. We have not activated Teammates, bought credits or assessed its security independently. Availability statements describe the vendor’s rollout, not confirmation that every eligible account already has access.