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
@bygregorr Yeah it’s like Sourcegraph was founded by the same people who like humans or something :P
A good proxy for “major industries” is how they segment the major publicly traded companies: https://t.co/Y9w4YKHSz2
If you're a builder who's tired of the AI discourse being about job loss, class warfare, and doomerism, come work with us as we figure out how to deploy AI to amplify the agency of humans working in major industries.
Amp Labs: small teams of the best software builders, working inside the most frontier-oriented company per industry and region.
https://t.co/IAI3YBqBWf
There are plenty of coding tasks where you need to be mindful of your mental model and actively steering the agent to implement a clean architecture. For those, you want something fast and interactive but still smart and competent.
What we learned from the previous rush mode is that cheap tokens do not necessarily mean cheap in terms of total cost or time spent. If you haven’t used rush in awhile, try it again!
We made rush actually rush.
It is now GPT 5.5 with no reasoning tuned for smaller, bounded coding tasks where higher reasoning is overkill.
It’s almost twice as fast and outperforms the previous Haiku-based rush on our internal evals.
The broader theme I'm seeing is that current agent UX makes the low friction path "LGTM". Software engineering has always had a verification problem in code review, but the rate at which agents generate plausible-looking code raises this to an imminent threat to both the mental bandwidth of humans and the integrity of the codebase.
As coding agent usage caps continue to tighten, Amp's pricing remains the same.
The "Porsche of coding agents" is increasingly near price parity with alternatives. Rather than switch tools every 3 months, Amp users can use one opinionated harness that's built for the frontier.
Markdown rendering in Amp is now 2x faster end-to-end, thanks to a new parser we (ahem...Amp) wrote today. This parser is 100x faster in most cases, and in large files 200x faster. Uses struct-of-arrays and buffers for low allocations and lazy string materialization.
@drnafizhamid@AmpCode This was a regression that went out today and will be fixed on the next version update. Sorry about the confusion and thanks for flagging!