Amp

The frontier coding agent.

[Quinn Slack @sqs]

We rebuilt Amp's UI so you can watch and drive all your Amp agents on web, mobile, and CLI.

https://t.co/nlNhe1hAA3

[Quinn Slack @sqs]

I love when technological progress kills a feature.

The models are so good that (A) this feature is too risky and (B) it's not needed anymore to convince people that agents are good.

https://t.co/PlPosB3wYu

[Tim Culverhouse @rockorager]

Some of you missed thread previews. They're back, baby.

[Thorsten Ball @thorstenball]

Amp Neo is now available to everyone.

Time to drop the suffix.

https://t.co/CFy5ButCCP

[Thorsten Ball @thorstenball]

https://t.co/PV4OLiTZnu

[Quinn Slack @sqs]

Proof-of-human with passkeys, for an extra layer of security when remote-controlling your Amp threads.

https://t.co/MnDiCH9PMA

[Amp @AmpCode]

Amp Labs: small teams of the best software builders, working inside the most frontier-oriented company per industry and region.

https://t.co/IAI3YBqBWf

[Quinn Slack @sqs]

We're still seeing and fixing bugs and instability in the Amp Neo CLI. If you're in the Neo beta, run `amp --take-me-back` to use the non-beta Amp CLI that is unaffected by these issues. (Or keep using Neo if you want. I am.)

I'm really sorry for these issues. We hit some unexpected scaling issues on this new architecture, and that's on us. We're working around the clock to get it stable and then open it up to more people. And huge thank you to everyone who's giving feedback and sending reports!

[Amp @AmpCode]

Update: not fully resolved.

Rolling out changes to increase capacity.

[Amp @AmpCode]

Incident resolved.

More machines for you all to run agents on.

Happy hacking!

[Amp @AmpCode]

@chrispycode Can you send us an email at amp-devs at ampcode dot com?

[Amp @AmpCode]

Incident resolved.

More machines for you all to run agents on.

Happy hacking!

[Amp @AmpCode]

We're going through some scaling issues with our new architecture.

Stand by.

Until then: `amp --take-me-back` to go back to the old Amp.

[Thorsten Ball @thorstenball]

The best coding agent in the world is back.

https://t.co/BU96nS5IcC

[Quinn Slack @sqs]

Smart mode in Amp now lets you use Opus 4.6 wth 300k input tokens of context, up from 168k. Also, tokens above 200k are now charged at the same (not higher) per-token rate.

Why not 1M tokens in smart? Quality/cost aren't right. If truly needed, use (hidden) large mode.

[Amp @AmpCode]

There's a new oracle in Amp: GPT-5.4.

https://t.co/FvxCDXBSqz

[Thorsten Ball @thorstenball]

And here is the model that killed it: GPT-5.3-Codex.

https://t.co/RfCol0gu3Y

[Thorsten Ball @thorstenball]

We believe the coding agent is dead.

Soon, Amp will look very different.

https://t.co/rSvdN7xcnJ

[Amp @AmpCode]

@sqs @thorstenball You can also watch it on YouTube: https://t.co/4nROo80RT3

Or listen to it on Spotify: https://t.co/hC6cKM9WeT

If you want to listen to all of them: https://t.co/Jam7aLMDQG

[Amp @AmpCode]

Episode 10 of Raising An Agent with @sqs and @thorstenball is out!

There's no better summary than this quote:

"We will be killing our editor extension, the Amp VS Code extension. We're going to be killing it. And we're going to be killing it because we think it's no longer the future. We think the sidebar is dead. Let's walk through why."

Topics in this episode:
- The new deep mode in Amp
- Balancing developer experience for humans & agents
- Killing the VSCode extension & shift away from traditional editors
- Pi & OpenClaw, two wonderful projects
- Importance of reinventing yourself in AI

Enjoy! And happy hacking!

Timestamps:

01:00 Deep Mode
10:30 Optimizing the codebase for agents
15:00 Feature Preview: which Skills does your team use?
18:00 Balancing DX for humans & agents
21:35 Killing the Amp editor extension
28:00 The future of software and what it means
33:00 You need to stay agile
36:00 Pi & OpenClaw
39:00 Text editors holding companies back
44:00 Is manual context management coming to an end?
49:00 New concept for Threads
50:00 Amp, the business & the art installation

[Amp @AmpCode]

Lewis wrote about how he gives Amp *visual* feedback:

[Lewis Metcalf @lewis_b_metcalf]

My workflow on @AmpCode is now about setting up playgrounds for myself and Amp.

I use the playgrounds to experiment, find limits, and break stuff. Amp uses them for rapid iteration and exploration.

I love working this way and wrote about it:
https://t.co/mWKPIbJwc9