The inbox has always been a strange kind of workplace. It is where a request starts, where the relevant spreadsheet gets buried, where five people debate a contract clause, and where the final version of a document is often sent around with a name like “FINAL_v7_revised_reallyfinal.” Now Perplexity wants to make email the place where that work gets done, too.

The company has launched Computer in Email, a feature that lets users send, forward, or cc computer@perplexity.com to assign a task directly from an email thread. Instead of opening a separate AI workspace, copying context into a prompt, uploading files, and waiting for an answer elsewhere, users can ask Perplexity Computer to do the work from the conversation already in progress. The result arrives back in the same thread, including attachments such as Excel models, PDFs, and presentation decks.

It is a simple idea, but it addresses one of the biggest frictions in workplace AI: context rarely lives neatly inside an AI chatbot. The information needed to complete a task is more likely to be scattered across a client email, a forwarded discussion, a set of attached documents, and a few implicit instructions that everyone on the team already understands. Perplexity is betting that the email thread itself can serve as the prompt.

A private equity associate, for example, could forward a confidential information memorandum and a data-room discussion, then ask Computer to build a first-pass leveraged buyout model. A legal associate could cc the agent on a long redline exchange and request a summary of unresolved issues before a call. An investment banker could ask for a five-year discounted cash flow model without ever leaving their inbox. These are the kinds of tasks Perplexity is positioning the feature for, and they reveal its larger ambition: not merely answering questions, but taking ownership of defined pieces of knowledge work.

The timing makes sense. Email is still the default coordination layer for much of the corporate world, even after years of Slack, Teams, project-management software, and collaborative documents. Deals move through email. External clients live in email. Contracts, finance models, approvals, status updates, and version histories all tend to accumulate there. That means even employees who spend their days in more modern collaboration tools often return to the inbox when the work becomes formal, cross-company, or consequential.

Perplexity says its system reads the full thread and any attachments after verifying the sender. It then runs the task using that user’s own connectors and permissions, rather than treating a forwarded email as an open invitation to access unrelated company information. The company also says tasks draw on the user’s existing Computer memory, including team terminology, preferred formats, and facts or decisions established in earlier sessions.

That memory layer may be the more consequential part of the announcement. Most generative AI tools are useful in isolated moments: summarize this document, draft that reply, explain this spreadsheet. But work rarely happens in isolated moments. A finance professional may have already set assumptions for a model. A lawyer may have adopted a particular negotiating position in an earlier draft. A consultant may have a client-specific slide format that is never written down in a fresh prompt.

If an agent can reliably carry that accumulated context from a web session to Slack, Teams, and now email, it begins to look less like a chatbot and more like a persistent work layer. Perplexity calls its self-improving memory system “Brain,” and says it allows an email task to reflect decisions from prior work rather than starting from zero each time.

There is an important caveat, though. An inbox is also one of the messiest places to hand an autonomous agent a task. Threads contain outdated instructions, irrelevant replies, forwarded messages from people outside the organization, and attachments with sensitive information. In high-stakes settings such as law, banking, healthcare, and corporate strategy, the usefulness of this kind of system will depend not just on whether it can produce a polished first draft, but whether it can distinguish an authoritative instruction from background noise.

Perplexity’s design acknowledges some of that risk. The company says Computer verifies the sender before carrying out a request and replies only to that sender for now. Enterprise support for reply-all is planned for later, a cautious choice that avoids an agent unexpectedly distributing an output to everyone copied on a thread.

That restraint is sensible. Email has a unique ability to turn a small misunderstanding into a company-wide problem. A poorly scoped AI-generated summary can miss a key caveat. An inaccurate model can look credible because it arrives as a finished spreadsheet. A document produced from an incomplete thread can accidentally preserve an assumption that a human had already rejected three replies earlier. The promise of agentic AI is that it reduces the drudgery of assembling, synthesizing, and formatting information. The danger is that it can hide the judgment calls that still need a person in the loop.

Still, the inbox may be one of the most practical places for AI agents to prove their value. Users do not need to learn a new interface, change their habits, or persuade every collaborator to join another platform. They can simply email a task in plain language, attach the relevant materials, and receive something usable back in the familiar record of the conversation.

Perplexity has been extending Computer across the places where office work already happens, including Slack and Microsoft Teams earlier this year. Email is the logical next step because it brings together the request, the supporting context, and the final deliverable in one durable thread.

For now, Computer in Email is available to all Perplexity Computer users. Its real test will be whether it can handle the uncomfortable middle ground between a quick AI assistant and a trusted colleague: the work that is too tedious to do manually, too nuanced to fully automate, and too important to accept without checking.