They run on separate machines and your agent just controls the remote runtime when it needs to interact with the system/write/read/etc

appreciate the clarity, that helps.

quick followup if the agent's running on a separate machine and interacting remotely, how are failure modes handled across the boundary? like if the agent crashes mid-operation or sends a malformed command, does the remote runtime treat it as an external actor or is there a strategy linking both ends for fault recovery or rollback? just trying to understand where the fault tolerance guarantees begin and end across that split.

token auth and re-handshake. Agent is respawned if it's no longer alive, and project index is resynced