Software tools for ongoing work have long struggled with the gap between one-off interactions and sustained efforts that stretch across days or weeks.
People often restart conversations, re-upload documents, or reassemble context from scattered notes, while collaboration adds friction when each participant works from different files or assumptions.
Perplexity addressed these limits by evolving Spaces into Projects within Computer.
Projects serve as hubs for long-running work, offering a single place to manage, create, and collaborate on tasks with a shared persistent file system and accumulated memory.
Existing Spaces migrate automatically, carrying over their content.
The hierarchical file system lets users upload documents, import folders, or pull from connected sources.
Computer opens files, reads current versions, edits them, and saves changes back to the same locations rather than starting over.
In a shared Project everyone works from the same source of truth, so one session can continue from files produced in another. Mac and Windows desktop users can link local files that remain visible only to them.
Projects also connect to more than 400 tools including Google Drive, Notion, Linear, Snowflake, and GitHub.
Memory comes from Brain, which reviews shared sessions and files between tasks and maintains a living record of the work.
Each new task begins with that accumulated understanding. Brain can organize files, keep tasks on track, run on a schedule or on demand, and update the Project summary.
To set up a Project, users can create a new one or convert an existing session so its files and artifacts transfer. Users then can set instructions that define how Computer should behave, the preferred formats, guardrails such as requiring approval before publishing, and default modes or models. and then enable Brain.
Files of many types become durable context, tools can be linked, and a Slack or Microsoft Teams channel can be bound so its conversation feeds the Project while tasks started there appear in the history.
Project-level instructions supply overall guidance, while Skills provide reusable steps, structures, and formats for recurring work. Instructions frame the broader context; Skills handle repeatable processes.
Collaboration keeps private data separate. Inviting others grants access to shared files, artifacts, automations, and history, but each person’s memory and connectors stay private.
Connector calls run under individual credentials. Threads can be forked without inheriting private elements. When bound to a Slack or Teams channel the channel supplies shared context, yet each request runs in a private session tied to the user’s identity. A Project can only operate within an organization’s existing access rules.
In a connected channel, typing /project binds it to a Project. Participants can add threads as context or request recurring automations such as weekly status updates, all while drawing on the Project’s files and memory.
These changes move the focus from isolated queries toward continuous multi-session activity that can involve multiple people, with Computer working on a stable set of files and carrying forward what it has learned while individual accounts remain private. Projects are available to all Computer users.
