Skip to main content
A project groups the threads, files, and shared context for one piece of ongoing work, so nobody has to re-explain the background every time they start a new thread. This page covers creating a project, giving it context, and finding it again later.

Create a project

1

Name it and say what it's for

Give the project a name and a short description of what it’s for. This is what shows up on the projects grid and what tells teammates whether a thread belongs here.
2

Set project instructions

Project instructions are persistent context applied to every thread you start in the project. Use them for things you’d otherwise repeat in every message: background on the work, constraints, or how you want output formatted.
3

Add sources

Add sources the project should keep on hand: documents and links every thread in it can draw on, without anyone having to attach them one thread at a time.
4

Connect a repository

Connect a repository to the project and its files become available to threads in the project. This saves you from attaching the same files by hand in every thread that touches that codebase.
5

Run threads inside the project

Start threads from inside the project. Each one picks up the instructions and sources you set, and its files and outputs stay grouped with the rest of the project’s work.
Project instructions, sources, and a connected repository all apply to every thread started in the project. You don’t set them again per thread.

Find and open a project

The projects grid lists every project you can see. Use the filters to narrow it down: All, Created by you, or Shared with you. Sort by last modified, name, thread count, or file count to find what you’re looking for. Open a project to see its threads, sources, and files in one place, and to start a new thread inside it.

Where to go next

Sharing and collaboration

Share a project or thread with teammates and work in it together.

Thread and composer

The anatomy of a thread and how the composer sends work to it.