Work continues between two messages with Perplexity Teammates

In Perplexity, Teammates follow missions over time, respond to changes, and collaborate in Slack. Access limited to Max on the web.

A durable responsibility can now be assigned to an agent in Perplexity. The new Teammates are designed to monitor work in progress, react when a situation changes, and continue the actions already underway without waiting for a new request. Their missions can involve a sales campaign, handling website bugs, or tracking project deadlines.

This feature extends Computer, Perplexity’s agentic work environment. Existing projects, files, memory, and Skills, these reusable instructions, serve as the starting point. The user describes what the agent should take care of, the useful tools, and the expected outcome. According to the publisher’s presentation, the follow-up also includes progress updates and requests for decisions when human intervention becomes necessary. A workflow that stays open

Each teammate appears in the sidebar and keeps a persistent conversation thread. This thread gathers ongoing actions and completed work; the user can ask for a status update or modify the mission there. The project history remains available from one run to the next, along with the objectives and shared files.

Memory is also supposed to incorporate corrections made to the work. The example given by Perplexity is that of an agency requiring two weeks’ notice: once this constraint is flagged to the teammate in charge of operations, that teammate is expected to apply it to subsequent schedules. Feedback thus becomes instructions for future tasks, without having to be repeated with each new request.

Access is offered on the web to Max subscribers. The price of this subscription is $200 per month or $2,000 per year. The launch page announces Teammates usage offered during a promotional period, then consumption of the credits already included in Max. The duration of this initial offer is not specified. The handoff also goes through Slack

Collaboration happens between agents and with the people working on the project. One teammate can pass its conclusions to another: in one of the scenarios presented, an agent spots bugs on a website and a second prepares the fixes. For a larger project, coordination can involve several Computer sessions and other teammates.

In a Slack channel to which the agent has been added, colleagues can assign it work or ask where a task stands. Follow-up therefore does not depend solely on the exchanges of the person who created it. Responses and approval requests can circulate in a space already used by the team.

The commercial demonstrations also feature continuous ad monitoring: reviewing results, pausing underperforming ad sets, and preparing new creative assets. These sequences illustrate the missions envisioned by the publisher, without establishing the results a real campaign would achieve. A separate workspace for each teammate

Each agent has its own environment, with a desktop and a browser. Browsing sessions and local cookies are independent from those of other teammates. This separation applies to task execution; it does not prevent agents from collaborating and handing work off to one another.

Computer’s existing permissions continue to apply to tools and projects. During setup, the user connects the necessary services, such as Slack, GitHub, or Gmail, and chooses which repositories are accessible in the case of GitHub. They can then review the work, take back control of the desktop, or redirect the agent while it is running. The brief specifies when to involve a person

The assigned role includes the circumstances in which the agent must act and those in which it must ask for a decision. In the demonstration devoted to a technical on-call rotation, the instruction calls for investigating alerts, preparing a fix and a rollback plan, then asking the user if validation is required or if the cause remains unknown after fifteen minutes.

The fix shown is presented as a proposal to approve before deployment. This scenario distinguishes the investigation, the preparation of a change, and its production rollout. The level of delegation depends on the mission instructions and the access granted to connected tools.