From the source
Amp now gives its coding agent a Mac, so it can build, test and run iOS and Mac apps while the thread itself keeps running on a Linux orb.
- The Mac is a second machine attached to that orb: Amp decides on its own when work needs macOS, and the server then boots a fresh cloud Mac with Xcode and the simulators installed in about 30 seconds.
- Code stays in sync, so Amp still edits on the orb and only builds, runs and tests on the Mac, with screenshots, logs and builds returning to the thread and the app reaching the orb's backend through portals.
- The thread's Mac tab streams the Mac's screen, and users can take control to try the app themselves.
- Every Mac starts fresh and nothing on it is saved; when Amp is done it keeps the Mac running for 20 more minutes so a follow-up can reuse the same machine and build cache, then deletes it.
- Amp says it tried running whole threads on Macs, called Morbs, but Docker and backends took minutes to start and keeping a Mac disk per thread got expensive. macOS Satellites are in beta with a waitlist in Settings, and Mac time draws on the same orb usage at a higher rate, then on Amp credits.