Amp for Windows
On November 17, ten days after an experimental release, Amp announces its Windows application, native on x64 and Arm, with a built-in runner, MSIX packages deployable through Intune, and Group Policy settings.
Every Amp story from the daily AI digest, newest first.
On November 17, ten days after an experimental release, Amp announces its Windows application, native on x64 and Arm, with a built-in runner, MSIX packages deployable through Intune, and Group Policy settings.
Amp is retiring the Dial, the four-mode control (low, medium, high, ultra) launched in July.
After orbs for development and portals for sharing work in progress, Amp adds boxes to provide lasting hosting for what users have built.
Portals, previously limited to orbs, now work on users' machines: a development server launched by the agent opens from the thread's Portal tab, accessible in a browser and in the iPhone and iPad apps according to the documentation.
On November 7, Quinn Slack, Amp's CEO, released an experimental Windows app with a self-updating installer; reported bugs earn credits, and a solid version is promised in about three to four days.
Amp launches Spaces: a space is a conversation with a single agent whose role is to launch and coordinate other agents.
A script tag, followed by a page URL with ?amp appended, lets users click an element on a site and write an instruction: Amp opens a thread in the project, and the agent makes the change in an orb, on a copy of the repository.
Amp integrates with GitLab, both on gitlab.com and on self-managed instances: its cloud environments, orbs, clone and push on the user's behalf, open and track merge requests, and Orb Spawner starts an orb for each new request or issue; no…
Documents attached to the thread (plans, reports, call notes) that the agent, user, and teammates edit together; the agent reads changes before resuming instead of overwriting them.
Workspace-owned accounts with their own API keys for team automations: reviewing every pull request, documentation, or a CI job that opens a thread via amp -ox.
October 30 catch-up: Quinn Slack, Amp's CEO, announces home screen widgets on X that, according to his screenshots, display several threads with their status or a single thread and its current action.
Amp adds Macs to its orbs, the cloud machines where its threads run.
Amp generates charts, timelines, diagrams and clickable mockups on demand, directly in the thread; no pricing or limits announced.
Six days after their launch, Amp's self-hosted orbs can be added through personal settings, without a workspace or administrator privileges; threads created on them carry the Personal label.
Following iOS and macOS in late August, Amp is releasing its Android app, available to download from ampcode.com/app, with its conversation threads, orbs and Puck.
Amp now lets users host their own orbs, the remote machines its agents run on: the customer provides the compute, and Amp turns it into orbs, provided the infrastructure can quickly start new machines, suspend and resume them, retain them…