Amp 2026-10-25: self-hosted orbs and an agent in Linear#
Published by Alex Sorokoletov
Part of the Amp Version Tracker series. | ampcode.com | News
Amp build 0.0.1792886472, one week on from 0.0.1792281673, lets you run orbs on your own infrastructure and makes Amp an agent inside Linear, where assigning or mentioning it on an issue starts a thread. These changes were published between October 19 and October 22, 2026.[1][2]
What shipped this week#
| Change | What You Get |
|---|---|
| Self-hosted orbs | Run orbs on your own compute with the amp orb provider command and a dispatch program you supply (Oct 22).[1] |
| Amp in Linear | Assign an issue to Amp or mention @Amp to start an Agent Session and spawn an orb (Oct 19).[2] |
Run orbs on your own infrastructure#
An orb is a remote machine Amp creates for a thread, carrying your code, your tools, and a full development environment, where the agent does its work.[3] As of October 22, you can supply your own compute and have Amp turn it into orbs inside your infrastructure.[1]
You run amp orb provider where your compute lives. It opens a connection to ampcode.com and waits for requests to spawn, pause, or delete orbs, then runs a dispatch program you supply to carry out each one. Every orb connects back to its thread on ampcode.com, and the post states that no inbound ports are needed.[1]
| Variable | What It Does |
|---|---|
AMP_ORB_PROVIDER_TOKEN | Holds the Custom Orb Provider token you create in workspace settings, so amp orb provider authenticates to your workspace.[1] |
ORB_OPERATION, ORB_ID, ORB_TOKEN | Passed to your dispatch program when the provider needs it to spawn, pause, or delete an orb.[1] |
The post includes dispatch scripts for Docker, E2B, Apple containers, Modal, Vercel, Daytona, and exe.dev, and a Helm chart for GKE, EKS, and AKS with Terraform examples; paused orbs are saved to snapshot storage so they resume on another worker node.[1] It lists three cases where a workspace might self-host: regulations that restrict where code runs, access to internal networks, and custom hardware, and points Enterprise plans to it.[1] Self-hosted orbs are free for individuals and teams; Enterprises pay standard orb pricing starting October 29, and until then they are free for every workspace.[1]
Amp as an agent in Linear#
As of October 19, Amp is an agent in Linear.[2] Assigning an issue to Amp starts a new Agent Session in Linear and spawns a new orb, and mentioning @Amp starts a session too. Amp posts its responses in that session and replies to messages you send along the way, and the session shows up in your Amp sidebar, where you can open it as a thread.[2] Setup is installing the Amp agent in your Linear workspace and connecting your Amp account to the Linear MCP under Settings, MCP & Integrations.[2]
The orb detaches from the Amp client#
Both changes move the orb away from the Amp app. Self-hosting places the machine that holds your code and runs your tools inside your own network, reached over an outbound connection to ampcode.com with no inbound ports open. The Linear integration starts an orb from an issue without opening Amp at all.
Put together, the thread and its orchestration stay on ampcode.com while the orb that executes the work can run on compute you operate and start from the tracker where you file issues. For a workspace with rules about where code may run, that separates the hosted control path from an execution environment you own.
Amp ships many builds a day, so a week spans dozens of them. The two entries above are the user-facing changes on the public changelog for October 19 through 22, 2026.
Sources#
- Amp News: "Self-Hosted Orbs," October 22, 2026.
- Amp News: "Assign It To Amp," October 19, 2026.
- Amp Docs: "Getting Started With Orbs."
Previous Amp analysis: Amp 2026-10-18 (October 18, 2026)
All 6 Amp analyses: Amp Version Tracker · Official Amp changelog