Threads

Threads are the conversational unit in Atoi. They hold messages, model selection, reasoning strength, attachments, tool results, questions, approvals, and task receipts. A thread remains a thread as its context and participants change.

Home is the orchestration thread

The root of the signed-in product opens a persistent home thread. It is designed for ongoing orchestration across the work you manage: planning the day, finding the right project, deciding what deserves durable execution, and resuming an earlier line of thought.

Home is not a dashboard and does not replace project state. It is the conversational front door. Durable implementation does not run against Home as an implicit coding workspace; when work needs repository scope, use a project-associated or other non-Home thread.

Plain threads and groups

A plain thread is a direct conversation between you and Atoi. Create one when a subject deserves a separate history, title, and set of follow-ups. Plain threads can remain unassociated with any project.

Group threads add participants to the same conversational model. The product marks them as groups, provides participant management, and includes a Groups preset in the project Threads lens. Group status does not change how tasks, receipts, or project associations are addressed.

The practical rule is consistent: do not infer a different execution contract from the thread’s placement in the sidebar. Read the thread, its associated projects, and any attached task receipts.

Associate a thread with projects

The composer supports project context references through @ tags. Submitting a prompt with a project tag does two things: it resolves that project’s context for the message and durably associates the thread with the project. The association is sticky until you remove it explicitly.

A thread can be associated with more than one project. Atoi stores those relationships in a join rather than assigning one project as the permanent owner. The same thread then appears in each associated project’s Threads lens.

You can also manage associations from the thread’s Projects menu. Adding or removing a project changes filing and available project context; it does not move, fork, or recreate the conversation.

Follow work in the same thread

When a request becomes durable work, Atoi creates or links a task and returns its handle to the conversation. Use that handle for status, approvals, and the final receipt. Opening task detail adds the canonical ?task=<id> address while leaving the current thread visible.

Continue an existing task when the objective changes or needs refinement. Starting a replacement task for every follow-up breaks the connection between intent, changes, checks, and proof that the thread is meant to preserve.