Skip to content
AtoiDocumentation
Use Atoi

Threads

Your one thread, what it keeps, how long work becomes a Task, and how a project scopes it.

A Thread holds the request, the questions, your answers, the work, and the result, and links to a Project without movingThread01Requestwhat you want02Questiona real choice03Answerstays on record04Workhere or a Task05Resultwith its receiptProjectlinked, not movedwhen continuity helpsone place, in the order it happenedstill reachable on its own
One place, in the order it happened. Filing links; it never moves.

Your thread is the one conversation you have with Atoi. Your workspace has exactly one, and it keeps your request, Atoi's questions, your decisions, the work it ran, and the result in order. There is no sidebar of chats to choose from, and nothing to file before you start.

#Say what you want

On the web your home is a thread. Open it with nothing said and Atoi thinks, then asks what you want to do. To ask something of your own, press ⌘N to jump to the composer and say what you want to end up with. There is no setup step and no separate code mode.

Attach only the context the request needs. Type @ to add a project, a document, an agent, or a computer when it explains something your words cannot.

#What a thread keeps

Read a thread top to bottom and you see the whole chain:

  1. what you asked for;
  2. what Atoi needed to clarify;
  3. what you decided or approved;
  4. what ran;
  5. what came back, with proof.

Long work becomes a Task. The task keeps its own state, and its receipt comes back into the thread, so you never read a log to learn what happened.

A link you send unfurls once into a balloon with its title and site, and the panel's Links tab keeps every one, newest first. While Atoi works, the thread says what it is doing, such as Atoi is searching. Dividers mark the time and the point where you last read. Right-click a message to see its actions.

#Give it a project

When a request belongs to a Project, attach the project with @ and the work runs against that project's source and rules. The thread stays the one place you talk; the project is where the work happens, and its Tasks appear in the panel's Tasks tab. Atoi may propose the project itself when your words point at one.

#Share it

Everyone in your workspace can see the thread. Add a person as a workspace member and the conversation comes with it. Publishing is different: it makes a read-only public page. Read Sharing and invites before you widen access.

#Pick it up on another app

Threads work fully on the web and in the terminal. Open the same thread from Ideas or search on the web, or continue it in the terminal. The Apple and Android apps open the same thread record and are still catching up on what you can do there.

Some commands and routes still say "thread" and some older copy says "conversation". They are the same thing.

Read Asks and approvals next.

Was this useful?