A Teammate is only as safe as the accounts you connect to it, so this is the section to read twice. Each Teammate gets its own separate desktop and browser, which lets it use websites and apps that have no official connection to Perplexity. Perplexity says browser sessions and cookies stay inside that one Teammate rather than leaking between agents.
Access follows the permissions you’ve already set on connected tools and Projects. With GitHub, you can pick which code repositories a Teammate may touch. Perplexity also says saved passwords and logins are encrypted, entered through a protected path, and hidden from the agent itself.
You keep a few levers. You can read each Teammate’s thread, give feedback, redirect it mid-task, or take over its desktop yourself. Teammates send progress updates and ask for approval at key moments. If you share a Teammate’s conversation with someone else, they get read-only access.
During setup, you choose which tools a Teammate connects to, such as Slack, Gmail or GitHub, and for GitHub you can limit it to selected repositories. In Perplexity’s own overnight engineering demo, the Teammate prepares its fix and then holds it until a person approves it. Perplexity hasn’t shown how reliably those safeguards perform in real-world use.