Use project workspaces to organize shared context, associated threads, durable tasks, and saved views.
A project is Atoi’s durable workspace boundary. It keeps related instructions, files, documents, runtime context, threads, tasks, and follow-up work under one identity. It is not a special chat mode and does not own a single primary thread.
Read the four project lenses
The project navigation is organized around Home, Threads, Tasks, and Views.
- Home shows the project identity, description, shared resources, runtime context, recent threads, and links into the rest of the workspace.
- Threads lists conversations associated through the thread–project join. It supports search, sorting, density, visible properties, activity grouping, and presets for all, pinned, and group threads.
- Tasks shows durable project work. Status presets and receipt-backed rows make active, blocked, completed, and failed work inspectable without replaying the conversation.
- Views stores project lenses for recurring filters, sorts, grouping, density, and visible properties.
These lenses do not create separate copies. Opening a thread from a project returns to its canonical thread route. Opening a task resolves the same addressable task record used by the thread and terminal surfaces.
Keep shared material in Home
Project Home has an Overview and a Documents section. Overview brings together shared instructions, files, document summaries, runtime context, and recent threads. Documents contains project notes and briefs, alongside the instructions and connected context used by future threads and runs.
Use instructions for guidance that should apply across the project. Use files for source material that every associated thread may need. Use documents for briefs, decisions, plans, and notes that should remain readable as the work evolves.
Atoi also records project events for thread association, task creation, files, and documents in the backend project event ledger.
<!-- TODO(verify): Confirm the current user-facing location for the project event feed. The backend records projectEvents, but the web Home page no longer exposes the former Activity tab. -->Join threads to the workspace
Project membership is many-to-many. Tagging a project in the composer durably files the current thread under it. Creating a new thread from a project also seeds the association. A thread can therefore participate in several projects without being moved or cloned.
Removing an association is explicit. The thread continues to exist, retains its messages and receipts, and remains visible through any other associated projects.
Bind durable implementation context
Project settings hold repository and runtime configuration for implementation work. The product uses that binding to resolve a stable workspace and carry source identity into governed tasks. Before applying a task change set, terminal workflows verify repository, branch, revision, path, and file baselines.
Use the project when continuity matters. The workspace should make later inspection cheaper: shared context is named, threads are findable, tasks retain proof, and the next session does not depend on terminal history.