Amp Neo limits beta access after sqs says the team paused expansion for stability
Amp’s sqs said the team paused adding more users to the Amp Neo beta to improve stability while early testers kept posting real-project demos. The update matters because it turns yesterday’s scaling complaints into an explicit access constraint for the remote coding-agent beta.

TL;DR
- Amp has paused adding more users to the Amp Neo beta after hitting scaling and stability problems, according to sqs' stability update and sqs' reply about paused expansion.
- The access limit is explicit now: in sqs' beta-access reply, sqs said the team had stopped rolling Neo out more broadly, then manually whitelisted a tester anyway.
- Early testers kept posting live demos while the rollout slowed, including RayFernando1337's plane demo and RayFernando1337's first-impressions thread showing Neo streaming work from a home Mac to the web.
- Amp already shipped a rollback path for affected users, with sqs' warning tweet and sqs' command note both pointing beta users to
amp --take-me-back.
sqs' beta-access reply is unusually specific about the constraint, RayFernando1337's plane demo shows the remote workflow people are trying to get into, and RayFernando1337's first-impressions thread spells out the product pitch in plain language: no model picker, no slash-command choreography, just a web session driving a machine you control.
Beta pause
sqs moved the story from vague instability to an actual access cap. In sqs' reply about paused expansion, he told a tester the team had paused adding more people to the Neo beta to make it more stable.
That lines up with an earlier post where sqs' beta-access reply said Neo had run into scaling issues, more rollout was paused, and exceptions were being handled by hand.
Remote workflow
The demos explain why people kept asking for access despite the warnings. In RayFernando1337's plane demo, RayFernando1337 said he kicked off a run on a Mac mini at home and watched it stream over the web from an airplane.
Later, RayFernando1337's first-impressions thread said the setup still felt realtime over slow in-flight WiFi, with the laptop acting as the client and the Mac mini in San Francisco doing the work.
Default-heavy UX
RayFernando1337's most concrete product note is that Neo hides a lot of agent configuration. In RayFernando1337's first-impressions thread, he said he did not need to pick a model, manage context limits, choose a thinking setting, or decide whether to plan versus hand off work.
The same thread also compares Amp Neo to other agent setups that still make users choose the model and reasoning mode manually. That makes the current beta pause notable because the thing being throttled is not just another CLI refresh, it is a more opinionated remote-agent workflow.
Rollback command
Amp is not asking beta users to just wait out the bugs. In both sqs' stability update and sqs' command note, sqs gave the fallback command directly: amp --take-me-back returns users to the older non-beta CLI.
That rollback path is the clearest sign of how Amp is managing the rollout right now: keep Neo live for willing testers, but keep the old path one command away while the new architecture settles.