Amp 2026-11-01: cloud Macs, Android app, in-thread charts#
Published by Alex Sorokoletov
Part of the Amp Version Tracker series. | ampcode.com | News
Amp build 0.0.1793534443, one week on from 0.0.1792886472, adds cloud Macs that build, test, and run iOS and Mac apps from a thread, an Android app, personal self-hosted orb providers you set up without a workspace or an admin role, and charts, timelines, diagrams, and mockups rendered inside the thread. These changes were published between October 27 and 29, 2026.[1][3][4][5]
What shipped this week#
| Change | What You Get |
|---|---|
| macOS Satellites | Amp attaches an on-demand cloud Mac to your Linux orb to build, test, and run iOS and Mac apps (Oct 29, beta).[1] |
| Amp on Android | An Android app with the thread, a Portals tab, and a Changes tab, installed from ampcode.com/app (Oct 27).[3] |
| Personal self-hosted orbs | Add your own self-hosted orb provider from your personal settings, with no workspace or admin role (Oct 28).[4] |
| Visuals in the thread | Amp renders charts, timelines, diagrams, and mockups in the thread (Oct 29).[5] |
Build, test, and run Mac and iOS apps on a cloud Mac#
A thread runs on a Linux orb that holds the code, the dev server, and the toolchain. As of October 29, Amp can attach a Mac to that orb, and it decides on its own when a task needs one.[1] Amp's server boots a fresh cloud Mac with Xcode and simulators installed, which takes about 30 seconds. The orb connects to the Mac and syncs your code; Amp edits on the orb and builds, runs, and tests on the Mac. Screenshots, logs, and builds return to the thread, and the app on the Mac reaches your backend on the orb through portals.[1]
The thread's Mac tab streams the Mac's screen, so you can watch Amp work or take control and try the app yourself.[1] Every Mac starts fresh and nothing on it is saved. After Amp finishes, the Mac keeps running for 20 more minutes, and a follow-up in that window reuses the same Mac and its build cache; after that the Mac is deleted. Archiving the thread or asking Amp to stop the Mac deletes it sooner.[1]
| Size | CPUs | Memory | Price |
|---|---|---|---|
mac.medium | 6 | 14 GB | $2/hour |
mac.large | 12 | 28 GB | $4/hour |
Mac time counts against your plan's orb usage at a higher rate, then draws from Amp credits as orb time does. Every Mac starts as mac.medium; you can ask Amp for a mac.large, or turn off mac.medium under Mac Satellites in the Experimental Features settings. The feature is in beta, with a waitlist in the same panel and documentation at /docs/orbs/mac.[1][2]
Amp on Android#
An Android app arrived on October 27. Its screens show the thread, a Portals tab, and a Changes tab that renders a diff. You install it from ampcode.com/app or by scanning the QR code on the announcement.[3]
Personal self-hosted orbs#
An orb is a remote machine Amp creates for a thread, carrying your code and your tools. Managing a self-hosted orb provider was limited to workspace admins; as of October 28, any user can add one for personal use.[4] You add a provider from your personal settings under Orbs, with the same steps as a workspace provider. When you create a thread, your provider appears under Self-Hosted in the orb picker, marked Personal.[4]
Visuals in the thread#
As of October 29, Amp can render charts, timelines, diagrams, and mockups in the thread.[5] The examples include visualizing the commits in a repo over the last month, and the commits, messages, tests, files, and diffs behind a feature. A UI example asks for diff-stat button variants, such as small colored squares, across Android, web, and iOS, to pick one and iterate.[5]
Where the work runs and where you see it#
Two of this week's changes widen the orb runtime. macOS Satellites attach a Mac to the Linux orb for the parts of an iOS or Mac build that need one, and personal self-hosted orbs let an individual point a thread at compute they operate. Two widen the thread surface: the Android app puts the thread, portals, and changes on a phone, and in-thread visuals turn repository history and UI ideas into charts and mockups beside the code.
The combined effect is a full mobile-app loop with no Mac or device on your desk. Amp edits on a Linux orb, builds and runs on a cloud Mac it creates for the task, exercises the app in a simulator, and sends screenshots back to the thread, where the Mac is deleted 20 minutes after the last step. The thread stays the single control point on ampcode.com while the machines behind it change by task.
Amp ships many builds a day, so a week spans dozens of them. The entries above are the user-facing changes on the public changelog for October 27 through 29, 2026.
Sources#
- Amp News: "macOS Satellites," October 29, 2026.
- Amp Docs: "Mac Satellites."
- Amp News: "Amp on Android," October 27, 2026.
- Amp News: "Your Own Self-Hosted Orbs," October 28, 2026.
- Amp News: "Visualize This," October 29, 2026.
Previous Amp analysis: Amp 2026-10-25 (October 25, 2026)
All 7 Amp analyses: Amp Version Tracker · Official Amp changelog