Amp

Amp reversed its same-day plan to proactively verify user IDs for future frontier-model access and deleted any Stripe verification records. The rollback removes an immediate KYC step, but Amp says governments and model labs could still require identity checks later.

Amp added optional identity verification with a passport or government ID, using Stripe and storing only the verification outcome. The feature is aimed at possible future lab or government access rules after Anthropic's export-control cutoff.

Amp shipped customizable keybindings and a mode switcher that describes each mode, and showed a .amp/plugins plus .amp/settings.json workflow for commit-and-archive macros. The release makes thread management and local customization part of the CLI surface instead of a fixed default UI.

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.

Amp paused wider Neo rollout after hitting scaling issues, but beta users still showed remote sessions running from a home Mac mini through the web UI, including over airplane Wi-Fi. That makes Neo notable as a local-hosted coding-agent model, even if the control plane is not yet stable enough for broader access.

Users reported higher token use, partial long-document reviews, and rising spend on routine tasks after Claude Code regressions came into focus. Some developers still get strong results in constrained harnesses, but others may want to switch to Codex for long-running work.