If you have the patience to watch your agents work step-by-step, you're giving them too short a leash. So: ampcode.com/news/less-noise

I got some more hot takes out of @thorstenball

AMP_IGNORE_GUIDANCE_FILES Minor, might be useful for some people building automations with Amp ampcode.com/docs/customize/a…

Kids love Amp, too

Launched just now in amp - if you have the mac app installed, it can automatically spawn runners for you! No more pesky terminal windows lying around :^) ampcode.com/news/the-mac-app…

Time to share your Amp runners ampcode.com/news/shared-runn…

I have liked a lot of your guys’ harness takes at amp! High taste.

A new option, Orb Saver Mode, stretches your orb minutes further. Most of you should not enable it. It means you'll spend more of your precious seconds alive on this planet waiting for a computer. It makes Amp a bit less proactive in waking orbs for threads you're merely viewing. ampcode.com/settings/advance…

"Attention is your most valuable resource" Agreed

Couple weeks ago I showed @AmpCode to my wife and helped her with onboarding (she’s not an engineer or programmer). Today, her colleague sent her a link to a Claude thread and asked her for help. My wife sitting nearby started complaining that it’s impossible to write anything to the thread directly and you have to send prompts and instructions back to a person via a chat or somehow 😅 She just created a new workspace in Amp for her non-tech company.

Some other popular agents cost ~25-60% more than Amp, based on est prices w/their different compaction thresholds. Interesting and obv incomplete comparison (thus names withheld). Amp's compaction exploits persistent thread storage, pointing to details in the thread rather than just getting the summary.

still can't get over how fun (and productive) multiplayer amp orbs are frontend changes used to be sooo slow to iterate on

no idea why, but I made a new sqs at ampcode.com Meta account for Meta Model AI for @AmpCode and now it's permanently deleted and banned. can anyone at Meta help unban it? (Other people on the team have access, so not urgent.)

a nice message from a customer made me realize how "support" flips from a cost to being mutually beneficial when it's in the agent loop

I know people who spent $12k in tokens and built nothing. @Westpac spent $12k in tokens on @AmpCode and built a new intranet for their 35,000 employees (vs. ~$3–5M pre-AI cost). "Amp is unlocking a huge amount of value in engineering" from itnews.com.au/news/westpac-s…

What should we improve/fix in Amp's AI router/gateway/custom URL support before we ship it to everyone? I think the model selection and mapping sucks right now...what else?

Everyone should copy "The Amp Way" for bugfixes: 1. Make it easy to report a bug in-product 2. Fix bugs fast 3. Find every other affected user 4. Email proactive, personalized apologies & credits 5. Get delightful replies & increase chances they report bugs -> virtuous cycle Try this with one bug fix this week and see how it goes.

Even if you start orbin' now, you're still very early

This blew up beyond anything I expected. The responses are surprising too: 40% says that, duh, this is already the reality at my job. Yes, at mine too. Another 40% agrees with some adjustments and different timelines. Then 20% disagree. Of those that disagree, some, of course, call me an idiot and that I only build CRUD apps and so on. Not surprising, it's the Internet after all. But there are two other categories of criticism that I find fascinating. One is that people say I work on AI and that is why I would predict AI to take over. The shovel seller says you should dig, is the criticism. I get it. But in my case they have the causality backwards: I work on agents, and have done so for nearly two years now, because I thought and still think that this is the biggest lever for developer productivity I've seen in my career. I'm talking about shovels and am in the shovel business because I think everyone should have one, not the other way around. The other critique is... strange, somewhat: people get offended by the predictions I shared here and get mad at me as if these were not predictions but wishes. Listen: I do not wish for anyone to be priced out of building software when I predict that some people will be. The weatherman doesn't want it to rain when he says there's gonna be showers on Tuesday. I'm merely predicting what I think will happen. I didn't say it's good or bad. I didn't say PMs shouldn't exist or Italian shoemakers. I'm making a prediction on what I think is going to happen, that's different from wishing what will happen. That being said: I wasn't always delighted about how things were going. I loved typing out code (I'm faster than you, pal), I loved debugging by hand, I loved my editor and my shell and my color themes. And AI and agents took a lot of that away from me. But I also hate being inefficient and 1.5yrs ago it became pretty clear to me that to continue writing code by hand will be inefficient and a waste of time. So I adapted. And now, with the latest generation of models, I'm having a ton of fun again: Fabel and Astra let me do things I never would've done by hand and now they also do the shitty parts and don't leave me to do the remaining shitty 10% to get it shipped. I'm excited and optimistic and think there's a ton of stuff to build and now we have superpowers that let us build more, faster; superpowers that truly let us shoot for the moon.