Skip to content
AtoiDocumentation
Use Atoi

Computers

Where Atoi runs work: Cloud, your own Mac, or another machine you connect.

Preview
Cloud, your Mac, and connected Computer execution targetsexecution targetscloudcode and browseryour Maclocal tools and desktopconnected computerapproved rootsclaim / leaseone controller at a timeCloud, your Mac, and connected Computer execution targetsexecution targetscloudcode and browseryour Maclocal tools and desktopconnected computerapproved rootsclaim / leaseone controller at a time
A claim binds each run to one execution target.

A Computer is a place Atoi can run work. Cloud is always there and needs no setup. Your Mac becomes a Computer when you connect it. Each computer says what it can do: run code, use a browser, or use a full desktop.

#Run on Cloud

Cloud runs code and a browser for you. It keeps your files between sessions and costs nothing while idle. It cannot use a desktop, and it starts logged out of your accounts unless you share a session with it.

#Connect your Mac

Connect your Mac to give Atoi a shell, your files, git, and a real browser. It uses a dedicated window, never your own tabs. Use the Mac app, or pair it from the terminal.

Open Settings → Computers and choose Connect a computer. Name the computer, install the CLI with the one-line command shown, then press Generate code. A code like XXXX-XXXX appears with the deployment it pairs with and a ten-minute countdown. Run the command it shows on that computer:

bash
atoi connect --code XXXX-XXXX

An expired code says so, and a new one is one press away. Host token below is the manual path: a long-lived token you paste into atoi login. atoi connect keeps the computer online for context, Tasks, and checks. Back in Settings → Computers you see what is connected, what each one can do, and whether it is awake.

Settings, Computers, with Cloud as the available place
Settings, Computers, with Cloud as the available place

#Share a browser session

When Atoi needs one of your logged-in sites, it uses a session you shared, kept in an encrypted vault. Every use leaves a note in the thread ("used your GitHub session"). Revoke any site, or all of them, under Settings → Connections, where every captured session is listed with a Revoke control and Revoke all sessions clears them at once. Sending, deleting, and paying still ask first inside a logged-in session.

#Atoi picks the least powerful tool

In order:

  1. a connection or an API;
  2. structured shell, file, and git operations;
  3. a browser it can read;
  4. a browser it can only see;
  5. a full desktop;
  6. handing control to you.

#Take over

Only one party drives a browser or desktop at a time. Take over from the computer tile in the thread: click or type in the live frame and the computer is yours. Atoi's input stops before yours starts, and the tile says Computer returned to Atoi when you hand it back. The thread records the handoff.

#Work in parallel

Two tasks never write to the same working directory at once. Parallel work happens in separate copies, and Atoi brings the results together as commits, patches, and artifacts.

For the state of a run on a computer, open its Task, and if a computer is offline, read Troubleshooting.

Was this useful?