Aravind Srinivas (@AravSrinivas), Perplexity's co-founder and CEO, announced Projects on Perplexity Computer on July 30, 2026: "turning Computer into a multiplayer agentic operating system for work with persistent memory, files, and sessions scoped across hubs and users. Available to all users!"
It's the collaboration layer Perplexity's existing agent stack was missing — Computer Brain already gave individual users a self-improving, persistent context graph; Projects extends that same self-improvement loop to teams working inside a shared, bounded context rather than isolated single-user sessions.
Update — August 11, 2026: Perplexity's official Projects documentation now fills in the launch thread's missing operational details. It documents project roles and contributor limits, shared project files, project-level Brain controls, Slack and Microsoft Teams channel bindings, connector-specific instructions and shared credentials, reusable project skills, and a running Project Summary. This article has been updated throughout to separate those confirmed capabilities from launch-day inference.
TL;DR
| Question | Answer |
|---|---|
| What launched? | Projects on Perplexity Computer |
| Announced | July 30, 2026, @AravSrinivas |
| Framing | "Multiplayer agentic operating system for work" |
| Scoped by | Hubs and users — persistent memory, files, and sessions |
| File system | Shared — single source of truth for all collaborators on a Project |
| Integrations | Google Workspace, Slack |
| Customization | Support for custom skills and instructions per Project |
| Memory engine | Computer Brain — self-improvement loops now run per Project, across all collaborators |
| Availability | All users, per the announcement |
| Roles | Owner, Can edit, and Can view |
| Contributor limits | Up to 5 on non-Enterprise Projects; up to 9,999 on Enterprise-owned Projects |
| Channels | A Project can bind Slack or Microsoft Teams channels so their context and Computer queries appear in the Project |
| Computer cost | Credit-metered on paid plans; Perplexity says 100 credits = $1 as of August 2026 |
What "multiplayer agentic operating system" actually means here
Srinivas's own phrase is doing a lot of work, so it's worth unpacking against what's actually described in the thread rather than taking the framing at face value. Three concrete components were named across the announcement:
- Persistent memory, files, and sessions — scoped across hubs and users. Not per-user isolation; a Project is a shared container multiple people and multiple Computer sessions operate inside simultaneously.
- A shared file system. Described explicitly as "a single source of truth for all collaborators" — the same files, visible and referenceable by everyone in the Project, rather than each person's Computer session maintaining its own separate file context.
- Integrations, custom skills, and instructions. The launch named Google Workspace and Slack. Perplexity's current documentation is more specific: owners can bind Slack or Microsoft Teams channels, choose connectors, add connector-specific instructions and shared project credentials, and upload reusable skills scoped to the Project.
Put together, "operating system" is the right register for what's being described: not a single-purpose feature, but a substrate multiple people, files, integrations, and Computer sessions all run on top of, with a shared state layer underneath all of it.
Brain's self-improvement loop, extended to teams
The most technically interesting line in the announcement is easy to miss: "every project goes through self-improvement loops on its memory, leading to better contextual understanding over time, thanks to offline compute that Brain performs between tasks and sessions of the collaborators on a Project."
That's a direct extension of Computer Brain, which explainx.ai covered at its original June 19, 2026 launch — a continuously learning context graph that updates overnight and feeds into every subsequent task, delivering (per Perplexity's own benchmarks at the time) a 25% accuracy improvement, 16% better recall, and 13% cheaper per-task cost on tasks requiring past context.
The original Brain remains per-user: Perplexity's separate Brain documentation says it learns only from your own sessions, connected tools, artifacts, and corrections, and never pulls in another person's private activity. Projects adds a distinct project-level Brain. The Projects documentation says it builds live knowledge from Project activity, exposes that knowledge in a Brain tab, and can run automatically or manually from Project settings.
That distinction matters for privacy and billing. A Project owner can decide whether queries may draw from individual memory, while the Project Brain maintains the shared work context. Brain runs are billed to the Project creator. The documented model is therefore not "everyone's private Brain memories are pooled"; it is shared Project activity feeding a Project-scoped knowledge layer, with individual memory separately controlled.
Whether that scales cleanly — more collaborators contributing more Project activity doesn't automatically mean cleaner or more useful consolidated memory — remains an open question. Team-scoped memory systems face a tradeoff between breadth of context and noise from irrelevant tangents; the documentation explains controls and scope, but does not publish quality benchmarks for multi-user Project Brain.
Where Projects sits relative to Perplexity's other recent Computer work
Perplexity has been shipping fast on the Computer agent stack across July 2026. Projects is the newest piece, but it's not the only recent one:
| Update | Date | What it addresses |
|---|---|---|
| Computer Brain | Jun 19, 2026 | Per-user persistent memory — the original self-improving context graph |
| GLM 5.2 orchestrator | Jul 9, 2026 | Which model routes/executes Computer tasks — 0.344x Opus cost, native advisor escalation |
| Projects | Jul 30, 2026 | Collaboration and memory-scoping layer — multi-user, multi-session, shared files |
These are complementary, not competing systems. The GLM 5.2 orchestrator is about what runs a task and how much it costs; Projects is about the shared context that task runs inside and who else has access to it. A given Project could, in principle, use any Computer backend — including the GLM 5.2 orchestrator — for actual task execution, while Projects handles the surrounding scope: files, memory, integrations, and who's in the room.
What's genuinely new vs. what's a rebrand of existing pieces
Worth being precise about which parts of this announcement are net-new capability versus existing Perplexity infrastructure repackaged under a new name:
| Component | Status |
|---|---|
| Persistent context graph / self-improving memory | Existing — this is Brain, now applied at Project scope |
| Multi-user collaboration on a shared agent session | New — the "multiplayer" framing is the headline addition |
| Shared file system across collaborators | New, as a described feature — no prior explainx.ai coverage of file-sharing inside Computer |
| Google Workspace / Slack integrations | Partially existing — Perplexity has had connector integrations before; scoping them per-Project is the new part |
| Custom skills and instructions per Project | New, as a project-scoped concept — consistent with the broader 2026 trend toward agent skills as a packaging unit for reusable agent behavior |
The honest read: the memory engine (Brain) isn't new — the collaboration and scoping model wrapped around it is. That's a meaningful ship, but it's an evolution of Perplexity's existing agent architecture rather than an entirely new system built from scratch.
What Perplexity now confirms about permissions, files, and cost
The launch thread left most deployment questions unanswered. Perplexity's current Help Center now gives teams a usable baseline:
- Roles and sharing — Projects are Restricted by default. Owners can assign Can edit or Can view access; Enterprise administrators can restrict public sharing, external invitations, and organization-wide publishing.
- Contributor ceilings — non-Enterprise Projects allow up to five contributors. Enterprise-owned Projects allow up to 9,999. That makes the consumer/team experience materially different from the Enterprise deployment model.
- File permissions — project files are persistent and shared with members who have appropriate access. Viewers and editors can view files; only editors can modify them. Computer can also create, update, and manage files inside the Project.
- Project settings — owners can set up to 8,000 characters of instructions, choose Search or Computer as the default mode, select a default Computer orchestrator model, prioritize web links or domains, manage Project Brain, and enable a running Project Summary.
- Connectors and channels — Projects can bind Slack or Microsoft Teams channels, choose connectors, attach connector-specific instructions, and store shared project-level credentials. Uploaded skills can be scoped to the Project while personal and organization skills remain available.
- Computer is credit-metered — the "available to all users" launch line should not be read as unlimited free Computer execution. Perplexity's credit guide says 100 credits equals $1; light tasks typically use 100–350 credits and complex tasks 350–950. Consumer Pro has no recurring monthly allocation after any promotional bonus, while consumer Max starts with 10,000 credits per month.
Those published controls resolve several launch-day unknowns, but they do not eliminate the need for a low-stakes pilot. Teams should still test connector permission propagation, Project Brain quality, removal/offboarding behavior, and actual credit consumption with their own workload before moving sensitive or business-critical work into Projects.
How this compares to team features in Claude and ChatGPT
Perplexity is not the first AI product to ship team-scoped context. Anthropic's Claude for Work and OpenAI's ChatGPT Enterprise both offer shared workspaces, and Claude Cowork specifically targets collaborative agent sessions. The differentiator Projects is claiming is not "teams can use this together" — that bar has been cleared industry-wide — but persistent, self-improving shared memory that compounds across a team's activity automatically, without anyone manually curating what gets remembered. Most competing team features handle shared documents and shared chat history well; fewer claim an offline consolidation process that actively gets better at a specific project's context over time, the way Brain's nightly loop does. Whether that compounding advantage holds up under real team usage, with its noisier and more varied inputs than a single user's session history, is the open question worth revisiting once early adopters report back.
Summary
Perplexity launched Projects on Computer on July 30, 2026 — a collaboration layer turning the agent into what CEO Aravind Srinivas calls a "multiplayer agentic operating system for work." Current documentation confirms persistent shared files, Owner/Edit/View roles, project-scoped instructions, Project Brain and summaries, Slack/Teams channel bindings, connectors, shared credentials, and reusable skills. Project Brain builds from shared Project activity while personal Brain remains private and separately controlled. The workspace was announced as available to all users, but Computer execution is credit-metered on paid plans.
Related on explainx.ai
- Perplexity Brain — the self-improving memory system inside Computer
- Perplexity Computer GLM 5.2 orchestrator — 0.34x Opus cost
- Perplexity Search-as-Code — agentic search
- Perplexity Wandr benchmark — open-source research agents
- Agent skills — complete guide
- What is MCP? Model Context Protocol guide
- What is an Obsidian vault as AI agent memory?
Sources: Perplexity Projects documentation · Perplexity Brain documentation · Perplexity Computer credits · Aravind Srinivas's July 30 launch announcement
Feature details and credit pricing were checked against Perplexity's official documentation on August 11, 2026. Limits, availability, and pricing can change quickly — verify them in your account before rolling Projects out to a team.