Projects
Group Coder Agents chats into projects with shared instructions, skills, and memory.
On this page
Note
Projects are in early access. Behavior and APIs might change between releases.
Projects group related Coder Agents chats. Every chat in a project gets the project's instructions, skills, and memory, so you don't repeat the same context in each chat. Your projects appear in the Projects section of the Agents page sidebar.
What a project provides
| Capability | What it does |
|---|---|
| Instructions | Text added to the system prompt of every chat in the project. |
| Skills | Skills available only to chats in the project. |
| Memory | Durable notes that the agent saves in one chat and reads in later chats. |
Ownership
Each project belongs to one organization and is owned by the user who created it. You choose the organization when you create the project, and you can't change it later. Chats in a project must be in the project's organization.
Any organization member who can use Coder Agents can create projects in that organization. Each user can own up to 100 projects across all organizations.
A project is private to its owner. Coder records project, instruction, skill, and memory changes in the audit log.
Create a project
- On the Agents page, select New project in the Projects section of the sidebar.
- Enter a Project name and an optional Description, and pick an icon.
- Choose the Organization.
- Select Create project.
The project page shows a Details panel with the project owner, creation date, organization, skills, and instructions, and lists your chats in the project.
To rename or delete a project, open the project's menu on its page or in the sidebar and select Edit project or Delete project. Deleting a project deletes its instructions, skills, and memories. Its chats are kept and move back to your chat list.
Add chats to a project
- Start a chat from the project page. The composer is locked to the project's organization.
- In the general new-chat composer, choose the project in the project picker. The picker defaults to No project.
- Move an existing chat: open the chat's menu, select Move to project, and choose a project. Select Remove from project to take it out.
- Drag a chat in the sidebar onto a project folder.
You can move only top-level chats that you own, that aren't archived, and that aren't running. Sub-agent chats always follow their top-level chat. After a move, the chat's next turn uses the new project's instructions, skills, and memory.
The API equivalent is PATCH /api/v2/chats/{chat} with project_id.
Set project_id to the nil UUID (00000000-0000-0000-0000-000000000000) to remove a chat from its project.
Instructions
Project instructions are added to the system prompt of every chat in the project, including sub-agent chats. Use them for conventions, context, and preferences that apply to all work in the project.
To add or change them, select Create or the edit icon under Instructions in the project's Details panel. Chats read instructions on every turn, so a change takes effect on each chat's next turn.
Instructions use the deployment's prompt size limit, set with --chat-max-prompt-bytes (default 128 KiB).
Skills
Project skills are single-file SKILL.md skills that only chats in the project can load.
Manage them by selecting the Skills row in the project's Details panel.
A project skill can show as a one-click action above the project's chat composers, or be limited to manual use from the / menu.
For details on the format, limits, and how skills from different sources resolve, visit Project skills.
Memory
Each project has a set of memories: short, named notes that persist across every chat in the project. The agent manages them with four tools:
| Tool | Purpose |
|---|---|
read_memory | Read a memory's full body. |
save_memory | Save a new memory. |
delete_memory | Delete a memory. |
consolidate_memory | Delete and save several memories in one atomic step, to merge or replace them. |
The agent saves facts that matter in future chats without being asked, such as how people on the project work, corrections, decisions, deadlines, and where to find information outside the codebase. It doesn't save what it can derive from the code or Git history. The agent is told not to save secrets, credentials, or personal details in memory. You can also ask the agent to remember or forget something.
How memory reaches the agent:
- Each chat sees an index of memory names and one-line descriptions, and reads a full memory only when it needs it.
- A change made in one chat reaches other chats at the start of their next turn.
- Only top-level chats get the memory tools. Sub-agent chats don't read or write memory.
- Memories can't be edited. To change one, the agent replaces it.
- When a chat leaves a project, its next turn drops the memories it saw.
| Limit | Value |
|---|---|
| Memories per project | 200. The agent is prompted to consolidate as the project nears the limit. |
| Name | Lowercase letters, digits, -, and _, up to 64 characters. |
| Description | 150 characters. |
| Body | 8 KB. |
The dashboard doesn't show memories yet.
To list, read, create, or delete them directly, use /api/experimental/organizations/{organization}/chats/projects/{project}/memories.