Spaces are now Projects
Today we’re rolling out Projects, an evolution of Spaces. Projects are hubs for long-running, ongoing work in Computer. A single place to manage, create, and collaborate on tasks with a shared file system and persistent memory.
Projects are built for how people really work. Each Project has a shared, persistent file system where humans and agents collaborate on the same files, and a Brain that learns from your work so the next task starts with full context from the last.
Because every task works from the same context, Projects are ideal for running many tasks and workstreams at once, often as a team. When collaborating on a shared Project, every team member works from the same files, context, and skills while personal memory and connectors stay scoped to each person's account.
Persistent File System
Projects uses a persistent, hierarchical file system. Upload documents, import folders, or pull files from connected sources, and every task in the Project can build on them.
Computer works in the file system the way a teammate would. It can open files, read their latest versions, make edits, and save changes back to the same files. Computer edits the same file rather than starting over every task.
In a shared Project, everyone works from the same source of truth. A teammate's session can pick up the model your session produced yesterday. Scheduled tasks can maintain a status document no one has to remember to update.
Any user can add files to a Project. Mac and Windows users on the desktop app can also connect local files from their desktop, keeping Project context tied to the docs, spreadsheets, and notes on their machine. These local files are only visible to the user who uploaded them and not shared with other users in the Project.
Users can also connect Projects to over 400 tools and apps their team needs, including Google Drive, Notion, Linear, Snowflake, and Github.
Self Improving Memory with Computer Brain
Every Project can connect to Brain, Computer’s self-improving memory system.
Between tasks, Brain studies the Project's shared sessions and files and maintains a living memory of the work that was done. Brain applies what it’s learned to each new task. As a result, every subsequent task starts from accumulated understanding and improves. Users never have to reassemble context from scratch.
Brain also helps keep a Project’s files organized and tasks on track. It can run automatically on a schedule or on demand, reviewing everything it has learned and updating the Project summary.
Setting up a Project
Create a Project or convert an existing session into a Project and carry its files and artifacts with it.
Set instructions and defaults — tell Computer how to work in this Project (formats, guardrails like "never publish without asking first"), and set the default mode and model for new sessions.
Turn on Brain — enable Project memory and choose whether it refreshes automatically or on demand.
Work rarely starts from scratch. A customer brief might pull from an Excel model, a Word document, Salesforce data, and a web search. Projects bring those sources together as a foundation for your work:
Upload or import files — docs, decks, spreadsheets, PDFs, and folders become durable Project context.
Connect the tools your team uses — Drive, Notion, Linear, Snowflake, and 400+ others.
Add a Slack or Microsoft Teams channel — Computer references the channel conversation as Project context, and tasks kicked off in the channel land in the Project's session history.
Project Instructions vs. Skills
Adding Project-level instructions gives Computer more context about the overall Project. A higher-level order like “never publish anything without asking for permission first” will tell Computer to always route final decisions through a human in that Project.
Skills give Computer reusable instructions for how to work inside a project. Upload a Skill to give Computer preferred steps, structure, and formats.
Project instructions hold the Project context while Skills run repeatable processes. If you find yourself doing recurring work, turn it into a Skill instead of rebuilding the setup each time.
Built for Collaboration
Teams can easily share and collaborate on a Project with others. When team members are invited into a Project, everyone works from the same sources, artifacts, automations, and history. Projects organize connected sources without pooling every teammate’s private data into one shared source.
Sharing context never means pooling private data:
Inviting someone into a Project grants no access to anyone else's memory or connected accounts. Every connector call runs under the individual member's own credentials and permissions.
Team members can fork a shared thread to build on work without inheriting the original author's private connectors or memory.
If a Project is bound to a Slack channel, the channel supplies shared context, but each user's request runs in its own private session keyed to that user's identity.
A Project can only narrow what an organization already permits. It can’t expand access beyond existing controls.
Integrating with Slack and Microsoft Teams
Projects meet people where they already work and communicate. Type /project in a Computer-connected Slack or Teams channel to bind it to a Project, then kick off and manage work with full Project context from web, mobile, or desktop.
In a shared channel, anyone can say "Add this thread to the project" to supply context, or "Create a weekly status automation for this channel" to get recurring updates on the work.
Spaces are now Projects
For users of Spaces, everything carries over and existing Spaces migrate automatically. The same work now benefits from a persistent file system, self-improving memory with Brain, and deeper cross-channel collaboration.
Projects are available to all Computer users today.