Projects are useful when several chats share the same background, files or working rules. Collaboration and limits can vary by plan.
1. Create one Project for one durable objective
Open Projects from the left menu, create a project, and name it by the goal—not by a vague topic such as “miscellaneous AI.”
2. Add the stable source material
Upload the files that should remain relevant across conversations. Remove stale versions so the project does not carry conflicting source material.
3. Write project-level instructions
Put persistent rules here: audience, tone, definitions, output conventions, source policy and what the assistant should never assume.
4. Move or start the right chats inside the Project
Use separate chats for separate workstreams while keeping them under the same project context. This prevents one giant conversation from becoming hard to audit.
5. Review the project as context changes
When the brief, source files or rules change, update the project itself rather than compensating with longer and longer one-off prompts.
Project instructions: You are supporting [project goal]. Treat [file names] as the source of truth. Audience: [audience]. Always return [format]. Flag conflicts between sources. Never invent missing dates, owners or numbers.
Creating one project for unrelated work; keeping stale source files; repeating permanent rules in every chat instead of using project instructions; assuming every chat automatically has perfect recall of all context.
Finish check
A healthy Project has one clear objective, current source material, short durable instructions and separate chats for separate workstreams.