Perplexity's Computer Jumps Into Your Inbox to Handle Work Automatically
Perplexity's agent platform now runs from any inbox by CCing [email protected], returning deliverables as attachments in the same thread.
- Perplexity launched Computer in Email, letting users CC [email protected] to run agent tasks.
- Computer reads the full thread and attachments, then replies with Excel, PDF, or deck deliverables.
- Every email task is a full session viewable on web and mobile with an audit trail.
- The agent uses the sender's own connectors, permissions, and Brain memory from prior sessions.
- Follows earlier Computer in Slack and Computer in Teams integrations targeting existing workflows.
- Available today to all Computer users; Enterprise reply-all support is coming soon.
Perplexity has plugged its agent platform directly into email. Send, forward, or CC [email protected] on any thread and Computer will read the entire conversation, run the task, and reply back in the same thread with the finished work attached. The feature is live for every Computer user starting today.
The pitch is simple: Computer is an AI orchestrator that manages a team of AI agents on your behalf, coding in Claude Code and GPT Codex, performing deep research, orchestrating tools across 400+ connectors, and creating files. Until now, invoking it meant opening the web app, or pinging it through Computer in Slack and Computer in Teams. Email is the third surface, and arguably the one where the raw material of knowledge work already lives.
How the inbox handoff works
The mechanics are deliberately boring, which is the point. Computer verifies the sender, ingests the full thread and any attachments, and runs the task with that user's own connectors and permissions. Deliverables like Excel models, PDFs, and decks come back as attachments in the reply. Every email invocation is still a full Computer session that is viewable on the web and mobile app, with the same step-by-step audit trail as any task launched from the web interface.
Two details matter for anyone thinking about deploying this on a team: