โ† All Features Projects Practical guide
๐Ÿ—‚๏ธ
Projects

Give ongoing work a home

Use a Project when the background should persist across multiple chats, but each question or deliverable still deserves its own conversation.

ContextFilesMemory

Create one when context should persist

โ™ป๏ธ

Repeated background

You keep explaining the same client, initiative, course or research topic.

๐Ÿ“š

Repeated sources

You keep uploading the same files or referring to the same connected material.

๐Ÿ’ฌ

Separate workstreams

Several chats should share context without becoming one very long conversation.

Set up the context once

Name the ProjectUse a clear body-of-work name.
Add reusable sourcesUpload files and supported links.
Add Project rulesThese override global instructions inside it.
Split the workStart separate chats for distinct outputs.
๐Ÿง 
Choose memory deliberately

Project-only memory keeps the context self-contained. Shared Projects use it automatically. Remember that deleting a Project permanently removes its chats, files and instructions.

Decide what belongs at each level

A well-organized Project separates standing context from individual pieces of work so future chats remain understandable.

๐Ÿ“Œ

Project instructions hold local rules

Put guidance here when it should apply to every chat in this body of work. These instructions override your global Custom Instructions while you are inside the Project.

๐Ÿ“š

Project sources hold reusable material

Store files, supported links and saved responses that you expect to reference repeatedly. Keep one-off material inside the relevant chat when it does not belong to the wider context.

๐Ÿ’ฌ

Chats hold specific deliverables

Use a separate chat for each substantial question, analysis or output. This preserves shared context without turning the Project into one unmanageable conversation.