Projects, threads, and where work lives
Projects
A project is a scoped workspace: one goal, one set of files, one crew. "Plan the kitchen remodel", "Q3 newsletter", "My web shop" — each gets its own project. A project can point at a real folder on your disk (your code, your documents), or gezel can manage a private workspace for it.
Every project can carry:
About — a plain-language description of what the project is. Gezel reads it before every conversation, so the context is always there.
Mission objectives — the success criteria. Write these like you'd brief a team.
A main crew member — the one the project is assigned to. Usually they do the work themselves; in a bigger project they lead a crew. See Your crew.
Threads
A thread is one conversation, with one of your crew, inside one project. Threads persist: close the app, come back next week, and the conversation is still there. Each of them keeps their own threads per project, so your researcher's threads don't tangle with your copywriter's. A thread contains the context that the model uses to respond to your requests.
Artifacts
When Gezel produces something that is an "accessory" to your files — a report, a script, an image, a spreadsheet — it lands in the project's artifacts. Artifacts are plain files on your disk, listed in the project's Artifacts tab, separate from your own files so nothing you own gets touched unless you ask.
The default project
Not everything needs ceremony. Chats that don't belong anywhere in particular live in the built-in default project — a catch-all that's always there.