Projects
Group related files, chats, and instructions into a dedicated workspace so repeated work does not sprawl across unrelated threads.
What projects solve
Projects are built for work that needs continuity. Instead of recreating the same instructions and re-uploading the same files in every chat, a project gives that work a persistent workspace.
What lives in a project
- a title and description
- project-specific instructions
- local files for that workspace
- one or more chats connected to the project
Good candidates for projects
- client work with recurring source files
- product planning across multiple threads
- writing or design efforts that span days or weeks
- analysis work that depends on a stable document set
- Create the project
Start from the Projects overview and create a new workspace with a clear name and purpose.
- Add instructions and files
Give the project durable guidance and upload the files the work depends on.
- Chat inside the project
Open project chats so the assistant can work with that project context instead of starting from scratch each time.
Projects versus custom assistants
Projects are best when the context is tied to one initiative. Custom assistants are better when the behavior should be reused across many projects or people.