Skip to main content
A project gives related tasks a shared starting point. Use one for a product, client, design, or other stream of work that needs the same instructions and reference files. Each project can include:
  • a brief that tells Adam what every task in the project should know;
  • files that are available to tasks in the project;
  • related tasks; and
  • a project memory setting that controls where memories learned during those tasks can be used.
Projects are available on paid plans.

​
Create a project

1

Open Projects

Select Projects in the sidebar, then select New Project.
2

Name the project

Use a name that distinguishes this work from your other projects.
3

Add shared context

Write a brief and attach any files that every task in the project should be able to use. You can add or change both later.
4

Choose the memory scope

Select Project only to keep memories inside the project, or All tasks to let Adam use them elsewhere in your workspace.
5

Create the project

Select Create project. Adam opens the new project when it is ready.

​
Start or move tasks

There are three ways to add work to a project:
  • Open the project and select New task.
  • Choose a project from the project picker beside the model picker before starting a task.
  • Open a task you own, select its action menu, choose Move, and select a project.
The project picker appears only when you have at least one project. A task started inside a project receives the project brief and shared files automatically. To take a task out of a project, open the task menu, choose Move, then select Remove. Only the task owner can move it between projects.

​
Maintain the brief and files

Open a project to see its Tasks and Files tabs. The brief is editable on the project page. Select the text, make your changes, then click or tab away to save it. Keep the brief focused on information that should apply to every task, such as:
  • the outcome and current stage of the work;
  • requirements and constraints;
  • naming or documentation conventions; and
  • decisions that future tasks should preserve.
Use the Files tab to upload more reference files. Project tasks can use these files without you attaching them to every conversation.
Put project-wide context in the brief. Keep instructions that only apply to one piece of work in that task’s first message.

​
Choose how project memory works

Project memory controls where Adam may reuse memories learned while working in the project.
Only tasks in this project can use its memories. Use this for work that should stay isolated from unrelated tasks.
The setting does not change the project’s brief or shared files. To change it later, open the project action menu, select Settings, then choose a memory option in Project Settings.

​
Control access

On a shared team, the project owner can set the project to Private or Team.
  • Private limits access to the owner and people invited to the project.
  • Team makes the project available to the team.
Use Share to invite someone directly as Can edit or Can view. Editors can work in project tasks; viewers have read-only access. Projects do not support anonymous public links. People invited directly to a project can leave it from the project action menu. The owner can change or remove an invited person’s access from Share.

​
Find and manage projects

The Projects page lets you search projects and switch between grid and list views. Use a project’s action menu to pin or rename it. Project owners can also change settings or delete the project. Deleting a project removes the grouping and its shared access. Its tasks and files are kept, but they are no longer grouped through that project. For task-specific collaboration and public links, see Work with tasks. To search files across your workspace, see Find and export files.
Last modified on August 21, 2026