Terminal

Use `atoi` to sign in, ask in a Thread, answer an Ask, run a Task, read its Receipt, share from the TUI, and connect your Computer.

Use the terminal for explicit commands, structured JSON, keyboard navigation, or a connected Computer. Choose the atoi CLI or open the TUI with atoi tui.

Authorize the CLI in your browser, then confirm the current operator identity.

atoi account login
atoi account status --json

Use atoi account logout when you want to revoke that terminal identity. This is separate from pairing the machine as a Computer.

#Arrive in the TUI

Open the keyboard-first client.

atoi tui

Start in Home for the active conversation. Move among Projects, Threads, Tasks, Inbox, Search, Channels, Automations, Settings, Skills, and Doctor with the section shortcuts shown in the sidebar.

TUI Home with a Thread selected and the composer ready

#Ask in a Thread

Send from the TUI composer. Use an explicit CLI command when you already know the Thread.

atoi thread list --json
atoi thread send --thread <thread-id> --prompt "Audit this release and show the blockers"

Add --model and --reasoning when you need to override the Thread's current choices. Context references, the model, and the reasoning strength all travel with the message.

#Answer an Ask

Open Inbox in the TUI, select the exact item, and confirm its request identity before you approve or deny it. Use the CLI for the same action in a script.

atoi inbox list --json
atoi inbox approve <item-id> --request <request-id> --confirm

TUI Inbox with one Ask and its approval details

#Start and watch a Task

Choose a Project and execution place, then start the Task. Use wait until it needs you or reaches a terminal state.

atoi task start --project <project-id> --profile safe --place cloud --prompt "Run the release audit"
atoi task wait <task-id> --json

Use atoi task cancel <task-id> to stop it or atoi task continue <task-id> --prompt "Check the remaining blocker" to continue the same record.

#Read the Receipt

Open Tasks in the TUI or read the command output. Check Result, Changes, Checks, and Proof before you act on a change set.

atoi task get <task-id> --json
atoi task changes <task-id>

Apply or prepare a draft PR only after you inspect the immutable change-set ID and fingerprint. Both actions require explicit confirmation and return a Receipt.

TUI Tasks section with Result, Changes, Checks, and Proof

Open a Thread in the TUI and choose the public share action. Select the conversation or message scope, review the boundary summary, and confirm. Copy the returned link and read the redaction Receipt. Public sharing works in the TUI. The CLI has no command for it today.

#Connect your Computer

Pair this machine, then keep the companion online when Atoi needs its shell, files, git, browser, or screen.

atoi login
atoi connect

Use atoi companion status to check the local pairing. Use atoi connect --once when you want the Computer to claim one Task and exit.

#Open the implementation runtime

Run the product-owned durable runtime explicitly when you want to work directly in a repository.

atoi mono
atoi mono -p "Inspect this repository and summarize the entry points."
atoi mono --continue

The bare atoi command remains the product CLI. Tasks and Receipts remain the durable record around implementation work.

#What each client covers today

What you do	TUI	CLI
Send a message with context, model, and reasoning	Yes	Yes
Send a message with attachments	Yes	No
Run the full Task lifecycle, read proof, apply a change set, draft a PR	Yes	Yes
Manage Projects, bind a Workspace, and read its source	Yes	Yes
Search, answer Inbox decisions, and run Automations	Yes	Yes
Read preferences, Connections, Skills, and Plugins	Yes	Yes
Create, rename, or archive a Thread or a Channel	Yes	No
See who is in a group and who is present	Yes	No
Share a Thread or a message publicly	Yes	No

An MCP client reaches Project, Workspace, Task, proof, and change-set records, and its thread tool sends, replies, and steers. It has no attachment picker.

Some steps always finish in a browser: authorizing a provider or a Channel, approving a Plugin install, pairing this machine, checkout, and opening a published page.

Use the CLI reference for every command and flag, or open Troubleshooting when an account, Computer, or backend check fails.

Was this useful?

#Sign in