Projects
Group conversations, a default persona and knowledge around one piece of work.
A project is a container for work that outlives a single thread. It holds conversations, a default persona and the knowledge bases that work should draw on — so a new conversation inside it starts already configured.
Projects are available on every account, including solo.
Creating one
New Project → Create Project.
| Field | Notes |
|---|---|
| Name | Required. |
| Description | What the project is for. |
| Default Persona | New conversations in the project start with it. Optional — No default persona is a valid state. |
| Knowledge Bases | The collections this work should be grounded in. |
Working in one
New Conversation from inside the project creates a thread that belongs to it and inherits its defaults. An empty project reads No conversations in this project yet.
The project page lists its conversations, so it doubles as the index for a piece of work — which is what makes it more useful than a folder for anything long-running.
A folder organizes; a project configures. If all you want is to keep threads together, use a folder. Reach for a project when the work has a persona and a body of reference material that should apply by default.
Archiving and deleting
Archive Project puts it away without destroying it — confirmed with Are you
sure you want to archive “
Delete Project is permanent.
Archiving is almost always the right choice for finished work: the conversations and their context stay intact and searchable.
A note on the default persona
If a project’s default persona has since been removed from your library, the selector shows Current persona (not listed). The project still works; pick a replacement when convenient.