Skip to content

Your thread


One workspace, one thread. Atoi posts here, asks here, and keeps everything it did here.

The Atoi loop: orient, ask, decide, work, verifythe receipt returns to the thread you started in01OrientHome thread02Askone outcome03Decideask or approval04Workleast capability05Verifyresult and proofholds until you answerreadproposeactcomputerThe Atoi loop: orient, ask, decide, work, verify01OrientHome thread02Askone outcome03Decideask or approval04Workleast capability05Verifyresult and proofholds until you answerreadproposeactcomputerthe receipt returns to thethread you started in
One loop. The ask gate holds until you answer; proof returns to the thread you started in.

Guides

Atoi is one agent, and you talk to it in one thread. There is no list of chats to manage and nothing to file before you start. Your workspace has one thread, and Atoi posts in it, asks in it, and keeps everything it did in it.

#One thread, not many chats

Other tools give you a sidebar of conversations and a project for each one. Atoi gives you one place. Every request you make, every question Atoi asks, every decision you take, and every piece of work it runs lands in the same thread, in order. Long work appears as a card you can open in place, and the result comes back to the same thread with proof.

Projects still exist, but they are context, not containers. A Project holds the source, instructions, and documents that a piece of work needs. You attach one to a request when it helps, and Atoi may propose one for you to approve. It never files anything silently.

#Your thread never sits empty

Sign in on the web and you are already talking to Atoi. Open the thread with nothing said and Atoi thinks for a moment, then asks what you want to do first. Answer the card, or press ⌘N and describe your own outcome.

Capture pending: The thread after sign-in, with Atoi's first questioncapture pendingThe thread after sign-in, withAtoi's first question1440×900/
The thread after sign-in, with Atoi's first question

The header's + button opens Ideas, rows of cards Atoi builds from what you are working on. Every card is a view of a real record, and opening one opens it in place over your thread. A decision waiting on you stays in the thread itself, where you answer it.

#What is left to set up

While anything is still left to set up, the first row in Ideas is titled Set up and holds one card per remaining step, such as connecting your code or giving Atoi a task. Open a card to do that step. The row disappears once everything is in place, so an empty Ideas top row means there is nothing left to do.

#The loop

Every piece of work follows the same five steps.

  1. Orient. Open your thread and pick up where you left off, or open Ideas to see the rest of your work.
  2. Ask. Say what you want to end up with. Attach a Project, a file, or a Connection only when it adds context.
  3. Decide. Atoi stops when it needs a decision. Before a consequential action, it shows you exactly what it is about to do.
  4. Work. Atoi uses the least powerful capability that gets the job done: a Connection before a browser, a browser before a full Computer.
  5. Verify. The result comes back into the thread you started, with what changed, which checks ran, and the proof.
Ways to use AtoiwriteTurn a rough thoughtinto a finished draft.researchGather sources andreturn the usefulanswer.codeChange a codebase andrun its checks.operateWork through connectedtools with yourapproval.reviewInspect the result andshow what supports it.Ways to use AtoiwriteTurn a rough thought into afinished draft.researchGather sources and returnthe useful answer.codeChange a codebase and runits checks.operateWork through connected toolswith your approval.reviewInspect the result and showwhat supports it.
Five common jobs, one accountable Thread.

#One agent, many capabilities

Atoi stays the same agent whatever it uses.

You chooseAtoi uses
A model and a reasoning strengthYour own provider keys, see Models
A ConnectionRead or act in a service you authorized
A ComputerRun code or a browser on Cloud or your own machine
A TaskKeep long work running with a visible state and a Receipt

#The same thread everywhere

Your thread, its Projects, Tasks, and Asks are the same records on every client. Not every client can do everything with them yet.

RecordWebTerminalCLI and MCPAppleAndroid
ThreadsYesYesComingComingComing
ProjectsYesYesYesComingComing
TasksReceipts onlyYesYesReceipts onlyComing

Each app keeps its own controls. See Apps.

Read Atoi 101 next for your first useful session, start to finish.