Skip to content
Atoi
Open Atoi

Computers

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

PreviewWeb · Terminal
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 connect from the terminal:

bash
atoi connect

Open Settings → Computers to see what is connected, what each one can do, and whether it is awake.

Capture pending: Settings, Computers, with Cloud and a connected Maccapture pendingSettings, Computers, withCloud and a connected Mac1440×900/settings/computers
Settings, Computers, with Cloud and a connected Mac

#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, at any time. 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. When you take over, Atoi's input stops before yours starts, and 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?