Perplexity’s new Teammates are designed to keep a project moving between conversations. Announced on November 4, the agents coordinate work inside Perplexity Computer, retain project context and bring results back for review, according to the company’s launch announcement.
The distinction is ongoing responsibility: a teammate can monitor activity and investigate changes without waiting for another prompt. Perplexity describes agents passing work to one another and taking instructions from colleagues in Slack. Its examples include investigating customer problems and tracking unfinished operational tasks. These are vendor-described capabilities; DaySec has not independently tested them.
For security teams assessing the preview, the immediate question is which accounts and actions that responsibility should cover.
Web preview, with metered usage
Perplexity’s setup documentation, updated November 5, limits the initial research preview to individual Max subscribers on the web. Pro is excluded, and Enterprise plans are not included by default. The launch announcement says iOS support is coming, without giving a date.
The Max plan page lists a subscription price of $200 monthly or $2,000 annually. Teammates use the plan’s monthly credits, so included access does not mean unmetered background work.
Perplexity’s separate credit guidance says consumer Max starts with 10,000 credits per month. Computer tasks pause when credits run out; optional auto-refill purchases more. Account settings determine the applicable allowance and spending controls.
Set the boundary before connecting accounts
The setup guide tells users to review requested permissions and restrict GitHub access to needed repositories. It says teammates inherit plugin and Project permissions, run on isolated computers with separate browser sessions, and cannot view encrypted saved credentials. Users can take over their desktop work.
Those controls address access and separation; they do not establish that every proposed action is correct. DaySec’s assessment is that a useful pilot should specify the source of work, permitted changes, recipients and review points before connecting production accounts. A teammate preparing a suggested fix has a different operational impact from one changing a live service or messaging customers.
Start with a narrow assignment and inspect its outputs. Keep a human decision point for consequential changes, and review both account permissions and credit settings before expanding the role.
