1. On the **Agents** page, select **New project** in the **Projects** section of the sidebar.
1. Enter a **Project name** and an optional **Description**, and pick an icon.
1. Choose the **Organization**.
1. 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`.
| `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.