# CellCog Projects Guide 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. --- ## What Projects Are, and Are Not A Project is a body of work inside your organization: a department, a campaign, a client engagement, a product line. It bundles three things: - **Documents** that every agent in the project can reference - **Agent roles**: specialized agents with instructions you write once and memory that persists across sessions - **Members**: the people working on it, each with a role in the project 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](./CellCog_Organization_Guide.md). --- ## Accessing Projects 1. Click **Projects** in the sidebar 2. **My Projects** lists every project you belong to, with your role (Admin or Member) 3. Click a project to open it --- ## Creating a Project 1. Go to **Projects** 2. Open **Create New Project** 3. Enter: - **Project Name**: A descriptive name - **Project Instructions**: Optional guidance for every agent working in the project 4. Create it You become the project's first admin. --- ## Project Tabs Each project has six tabs. ### Chats 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. ### Documents Upload and manage files that agents can reference: 1. Select files or drag them in 2. Add an optional description for each file so agents know what it is 3. Upload **Supported file types:** - Documents: PDF, Word, Excel, PowerPoint, CSV, Markdown, plain text - Code: JavaScript, TypeScript, Python, Java, C, C++, C#, Go, HTML, CSS, JSON, YAML, XML, shell scripts, and more - Images: JPG, PNG, GIF, BMP, WebP, SVG - Audio: MP3, WAV, AAC, FLAC, M4A - Video: MP4, MOV, AVI, WMV, WebM, and other common formats The file picker shows the full list of accepted extensions. **File limits:** - Documents: 50MB max - Images: 20MB max - Audio: 50MB max - Video: 100MB max ### Members Manage who has access to the project: 1. **Add User to Project**: enter a **User Email**, an optional **Title** and **Role Description**, and switch between **Admin** and **Member** 2. Add several people at once by uploading a CSV (email, title, role description, admin flag) and reviewing the list before adding 3. Edit a member's title and role description, or remove them, from the list **Roles:** - **Admin**: Full access, can manage documents, members, agent roles, and settings - **Member**: Can use the project but cannot manage it **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. ### Agent Roles Create specialized agents for the project: 1. Open the **Agent Roles** tab 2. Create a role with: - **Title**: Agent name (e.g., "Sales Agent", "Technical Expert") - **Role Description**: What this agent does and its primary responsibilities - **Role Instructions**: Specific guidelines for behavior 3. Save 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: 1. **Instructions you don't have to repeat**: define the agent's behavior once, and it applies to every chat with that role 2. **Automatic long-term memory**: once a chat has been idle for a while (at least 45 minutes), the agent stores relevant learnings and artifacts into its own private document store. Next time you chat with the same role, it remembers previous work. 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](./CellCog_Memory_System_Guide.md) for a full walkthrough of how agent memory works. ### Agent Memory 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. ### Analytics Usage statistics for the project. --- ## Using Projects in Chats ### Starting a Project Chat 1. Click **New chat** in the sidebar 2. Click the **Project** selector in the editor toolbar 3. Select your project 4. Optionally select an **Agent Role** 5. Enter your prompt and send ### Quick Action from Project Page 1. Open a project 2. On an agent role card, click **New Chat** 3. A new chat opens with the project and agent role pre-selected --- ## Project Documents vs Organization Documents | 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. --- ## Editing Project Settings 1. Open the project 2. Open **Edit Project Information** 3. Modify: - Project name - Project instructions 4. Save Only admins can edit project settings. --- ## Deleting a Project 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. --- ## Deleting Documents 1. Go to **Documents** tab 2. Find the document 3. Click the **delete** button 4. Confirm deletion Only admins can delete documents. --- ## Agent Role Management ### Editing an Agent Role 1. Go to **Agent Roles** tab 2. Click **Edit** on the agent card 3. Modify title, description, or instructions 4. Save ### Deleting an Agent Role 1. Go to **Agent Roles** tab 2. Click **Delete** on the agent card 3. Confirm deletion **Warning:** Deleting an agent role deactivates the associated agents and cannot be undone. --- ## Best Practices ### Organizing Documents - Use clear, descriptive filenames - Add descriptions to help agents understand files - Keep documents up to date - Remove outdated files ### Creating Effective Agent Roles - Be specific in role instructions - Include examples of desired behavior - Define what the agent should and shouldn't do - Specify output formats if needed ### Team Collaboration - Assign appropriate roles (Admin vs Member) - Keep project instructions updated - Communicate about document changes --- ## Frequently Asked Questions ### Can I use one Project per company to run several companies from one account? No. Projects organize work inside one organization. Create one organization per company instead and switch between them from the profile menu. See [Organization Guide](./CellCog_Organization_Guide.md). ### How many documents can I upload? There's no strict limit on document count, but total storage is limited by your plan. ### Can I add an existing chat to a project? 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. ### I did the work in chats. How does a new AI employee see it? 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. ### Can I move documents between projects? Currently, you need to download and re-upload to move documents between projects. ### Who can see my project documents? Only project members (Admins and Members) can see project documents. ### What happens if I leave a project? You lose access to the project and its documents. Your previous chats remain but won't have document access. ### Can agents access all project documents? 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. ### What's the difference between project documents and agent role memory? **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](./CellCog_Memory_System_Guide.md) for details. --- ## Related Guides - [Getting Started](./CellCog_Getting_Started.md) - [Chat Guide](./CellCog_Chat_Guide.md) - [Organization Guide](./CellCog_Organization_Guide.md) - [Memory System Guide](./CellCog_Memory_System_Guide.md) --- Markdown alternate of https://cellcog.ai/support/projects-guide (CellCog support guide, category: Basics). All guides for agents: https://cellcog.ai/support/llms.txt. Site index: https://cellcog.ai/llms.txt. Try CellCog free, no credit card needed: https://cellcog.ai/signup