Skip to content
Atoi
Open Atoi
AppsAndroid

Android

Sign in on Android, ask in a Thread, inspect participants, and hand Task, Ask, Receipt, and sharing actions to the web or the terminal.

Use Android to start or continue a conversation with Atoi. Native navigation and sheets fit the device, while records are designed to converge with the web, Apple apps, and terminal.

#1. Arrive and sign in

Open Atoi and sign in on the authentication screen. After authentication, open Threads and choose a recent conversation or start a new one.

Capture pending: Android sign-in screen before the Thread section openscapture pendingAndroid sign-in screen beforethe Thread section opens412×915ClerkAuthScreen
Android sign-in screen before the Thread section opens

#2. Ask in a Thread

Describe the outcome you want, add context references only when they help, and choose a model and reasoning strength before you send. The message and its selected attachments travel together.

Open /c/<thread> from an Atoi link to reach the same conversation directly.

Capture pending: Chat screen with context, model, and reasoning controlscapture pendingChat screen with context,model, and reasoning controls412×915/c/<thread>
Chat screen with context, model, and reasoning controls

#3. Check who is in a group Thread

Open the group detail sheet and read the participant list before you send anything meant for a specific audience. Android verifies participant identity, but it does not verify group presence or typing state today.

Capture pending: Group detail sheet with the participant listcapture pendingGroup detail sheet with theparticipant list412×915GroupDetailSheet
Group detail sheet with the participant list

#4. Answer an Ask

When work waits on a decision, open the same Thread or Inbox item on the web or in the terminal. Read the request and target, then approve, deny, or choose an option. Inbox decisions are not on Android yet.

#5. Watch a Task

Follow the Thread until it points to a Task. Starting, stopping, and reading the proof of a Task are not on Android yet, even though the app has Task screens and opens Task links. Open the Task on the web to read proof, or use the terminal to start, wait for, cancel, or continue it.

#6. Read the Receipt

Open the same Task on the web, Apple app, or terminal and read Result, Changes, Checks, and Proof. Return to Android when you want to continue the conversation after you understand the Receipt.

#7. Share from the web or the terminal

Review the complete Thread, then open it on the web or in the TUI to create a public share. Public sharing is not on Android yet. Test the resulting /share/<share> link signed out before you send it.

#On this surface today

On Android today you can send a message with its attachments and composer options, attach context references, choose a model and a reasoning strength, and see who is in a group.

Not on Android yet: Thread and Project management, group presence, feedback, reactions, public sharing, starting or stopping a Task, Task proof, Inbox decisions, Channels, Automations, and settings.

#Where it differs

  • Compared with the web, Android verifies the core message composer and participant list, but not Thread lifecycle or the broader Library record set.
  • Compared with the web, Android does not yet verify Ask resolution, Task proof, change-set inspection, or public sharing.
  • Compared with the web, Android uses native bottom navigation, sheets, and deep links instead of browser routes and modal panels.

Was this useful?