A task on a self-hosted Orb

A task on a self-hosted Orb A sequence diagram generated by Archify. Connect out; wait for jobs Provider-initiated HTTPS; no inbound connection. Task; select local provider Dispatch spawn Via the provider’s existing outbound connection. Create + bootstrap Docker container; amp orb bootstrap. Connect out to Amp Repo-backed setup follows; probe was repo-free. Run tool command Local execution; model and agent loop stay in Amp. File contents, output, diffs Tool results leave for Amp and are stored with the thread. Result in thread User · Amp thread · Sequence participant User Amp thread Amp cloud · Model + agent loop · Sequence participant Amp cloud Model + agent loop Local provider · Your workstation · Sequence participant Local provider Your workstation Docker Orb · Your workstation · Sequence participant Docker Orb Your workstation Legend request return default message

Outbound connections

  • • Arrows show messages, not inbound network access.
  • • Provider and Orb both connect out to Amp.

Local execution, cloud reasoning

  • • Commands run inside the workstation’s Docker Orb.
  • • Read files, output and diffs can leave for Amp.