Email has long occupied a peculiar place in professional life. Even as collaboration platforms, messaging apps, and specialized software have multiplied, a substantial share of knowledge work continues to unfold inside inboxes.
A lot of contract negotiations move forward through successive rounds of redlines attached to messages, investment analyses take shape as spreadsheet models passed back and forth. Due diligence threads accumulate documents, comments, and open questions that must somehow be synthesized before the next call.
For some and good reasons, email remains stubbornly useful precisely because it already contains the context, the record, and the participants.
With that in mind, Perplexity extends its existing agent system into that same medium.
The system in question is known as Perplexity Computer.
It functions as a general-purpose digital worker rather than a conversational chatbot.
Users describe an outcome in natural language; Computer then breaks the request into subtasks, assigns those subtasks to specialized models and tools, and carries the work forward (sometimes over hours or longer periods) until deliverables are produced.
It maintains a persistent memory of terminology, preferred formats, and earlier decisions, connects to the user's own authorized services and data sources under the user’s existing permissions, and operates inside an isolated environment that includes a filesystem, browser automation, and code execution.
The same system had previously been reachable through the web interface, Slack, and Microsoft Teams.
On 18 August 2026 it became reachable by email as well.
The mechanics are straightforward.
A user who already has access to Computer can address a new message to [email protected], forward an existing thread, or simply carbon-copy the address into an ongoing conversation.
Computer first verifies the sender, then reads the full thread history together with any attachments.
It applies the same connectors, permissions, and accumulated memory that would be available if the task had been started on the web or in Slack. Once the work is complete, it replies inside the original thread.
Spreadsheets, PDFs, presentation decks, and other files arrive as ordinary attachments.
The email interaction simultaneously creates a normal Computer session that can be inspected later on mobile or desktop, complete with the same step-by-step audit trail that appears for any other task.
Concrete illustrations help clarify the scope.
A private-equity associate can forward a confidential information memorandum and the associated data-room thread, adding a short instruction to produce a first-pass leveraged-buyout model; an Excel file returns in the reply. A law-firm associate can carbon-copy Computer into a multi-round redline exchange with outside counsel and request a concise summary of unresolved issues across the last three sets of comments. An investment-banking analyst can write directly to the address asking for a five-year discounted-cash-flow model of a target company and receive the completed workbook without leaving the inbox.
In each case the output draws on whatever institutional language, modeling conventions, or prior assumptions the user has already established with Computer.
Since emails can contain sensitive information, Perplexity promises explicit security constraints.
For example, Computer replies only to the original sender; support for reply-all is described as forthcoming for enterprise accounts. And because the system authenticates the sender and operates under that individual's credentials, a task initiated by email inherits the same access boundaries that would apply on any other surface.
The feature is available immediately to existing Computer users.
The introduction of this extended ability illustrates is a broader pattern in the AI industry and the current large language models (LLMs) war: agent systems are beginning to appear inside the tools people already use rather than requiring them to open a separate interface.
Email, for all its well-documented shortcomings, still concentrates a large fraction of professional context. Making an agent reachable there simply removes one more context switch for those who choose to use it.
