Projects organize work inside your company: shared documents that agents reference automatically, specialized agent roles with their own memory, and the colleagues working on that body of work.
A Project is a body of work inside your organization: a department, a campaign, a client engagement, a product line. It bundles three things:
A Project is not a separate company. Your company on CellCog is your organization, and Projects live inside it. If you run several companies, create one organization per company and switch between them, rather than one Project per company; inviting outside people into Projects is not the way to build a multi-company setup. See Organization Guide.
You become the project's first admin.
Each project has six tabs.
The chats linked to this project. Open one to pick up where it left off. To bring an existing chat here, use Add to project on the chat's three-dot menu in the sidebar, or the Project chip in that chat's message editor.
Upload and manage files that agents can reference:
Supported file types:
The file picker shows the full list of accepted extensions.
File limits:
Manage who has access to the project:
Roles:
Who you can invite: anyone, by email. Someone who doesn't have a CellCog account yet shows as Pending and receives an invitation; they become Active when they sign up. Joining your project doesn't add them to your organization. A colleague from another company who joins your project gets access to that project only (its documents, agent roles, and chats), never to your organization's documents, task board, channels, Drive, or AI employees.
Create specialized agents for the project:
Agent roles can be selected when starting a new chat.
What agent roles actually do:
Agent roles are more than saved instructions: they are repeatable role assignments with their own persistent memory. Each agent role gets:
For example, if you have a project for a content series and create an "Episode Producer" agent role, the agent will remember previous episodes, your style preferences, and continuity details across sessions, without you having to re-explain anything.
The agent role selector in the chat editor shows how many memory docs each role has accumulated, giving you visibility into the agent's knowledge.
See Memory System & Context Trees Guide for a full walkthrough of how agent memory works.
The documents each agent role has stored for itself, organized by role. These are the agent's accumulated memories, separate from your project documents. You can review them, add to them, or delete files here.
Usage statistics for the project.
| Type | Who can use them | Where agents see them |
|---|---|---|
| Project Documents | Members of that project | Chats linked to the project |
| Organization Documents | Everyone in your organization | Every chat of every member |
Use project documents for the materials of one body of work. Use organization documents for company-wide resources such as brand guidelines and policies.
Only admins can edit project settings.
Admins can delete a project from its page. Deletion removes all agent roles and their memory, the project's documents and knowledge base, and all member access. It cannot be undone.
Only admins can delete documents.
Warning: Deleting an agent role deactivates the associated agents and cannot be undone.
No. Projects organize work inside one organization. Create one organization per company instead and switch between them from the profile menu. See Organization Guide.
There's no strict limit on document count, but total storage is limited by your plan.
Yes. Use Add to project on the chat's three-dot menu in the sidebar, or the Project chip in the chat's message editor. The chat then reads the project's documents and shows on this tab.
Three routes, from least to most effort: hire the employee into the same project (it reads the project's documents); use Save Artifacts on the chats to store their results as project documents; or paste a chat's link to the employee and ask it to read that chat, which works for any chat you own.
Currently, you need to download and re-upload to move documents between projects.
Only project members (Admins and Members) can see project documents.
You lose access to the project and its documents. Your previous chats remain but won't have document access.
Yes. When you start a chat linked to a project, all project documents are automatically available to the agents; you don't need to attach them to each chat. This is different from chat attachments, which only exist for a single conversation.
Project documents are shared assets accessible to all agents in the project, like brand guidelines, datasets, or specs. Agent role memory is private to a specific agent role and contains its accumulated learnings from past sessions. Think of project docs as "team knowledge" and agent memory as "personal experience." See Memory System Guide for details.