Computers

A Computer is a logical execution target Atoi can use for allowed work. It may represent cloud code and browser capability, a paired Mac, or another supported target. The product should describe what the target can do rather than exposing provider tables as the main mental model.

#Read capability and availability separately

A target can advertise capabilities such as structured process execution, files, Git, browser control, screenshots, streams, or desktop input. Availability says whether the target can accept work now. A capable but offline target is still unavailable.

The current settings surface can show registered computer state. Because the architecture is in preview, treat a connected row as configuration evidence, then verify the actual action before calling the target proven.

#Use the least-powerful sufficient target

Prefer, in order:

1. a native API or Connection;
2. structured shell, file, or Git operations;
3. DOM-capable browser control;
4. visual browser control;
5. full desktop control;
6. human takeover.

This reduces ambiguity, cost, and accidental authority.

#Respect scope and control

A paired local target should operate only inside user-approved roots. Interactive browser or desktop input has a single controller at a time. Taking human control pauses agent input before the lease transfers.

Provider keys remain server-side. Short-lived stream URLs are credentials and should not become public artifacts.

#Understand concurrency

Parallel mutating work should use isolated working directories or targets. Browser sessions need isolation, and desktop input remains exclusive. Atoi reconciles work through commits, patches, events, and artifacts rather than concurrent writes to one working tree.

Use Tasks and receipts to inspect the run bound to a Computer. Use Troubleshooting when a target is offline or degraded.