
we will need to rebuild and rewrite much of software to adapt to a new, faster pace.
code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases.
this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing.
your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos.
the time for mourning coding is long over
Replying to @josephfcox
Here is Proton CTO's AI manifesto, that I obtained multiple copies of 404media.co/manifestos-fear-…
Building agents for specific use cases in your software factory and business processes is extremely powerful.
The hard part is not the agent. It's the hosting, infrastructure, integrations, and security.
The Agent SDK makes it a breeze. Excited to see what you all build!
More and more of our production debugging at SpaceXAI now starts in Slack, with an agent.
An alert fires, and the agent is already watching the channel. It reads logs, metrics, errors, and code, then replies in the thread with what broke and why. Often we read its answer before we open a single dashboard.
We're now letting a few teams outside SpaceXAI add this debugging agent to their own Slack. If you want early access for your team, reply or DM me! 👇
here's how i shipped 2,500 PRs last month to production
this was originally supposed to be for Cursor Compile in London. i couldn't make it since i was livestreaming for Grok @Bot Galaxy so i'm making it available for free here on X! watch it on 2x speed, i talk slowly
Josh Ferge retweeted
When a nerd tells me they don't use agents "because I can write better code than any agent", I usually go "huh, sure buddy, you do you". When they tell they don't use agents for monitoring, I just laugh in their face.
Seriously. You can't monitor a production deploy better than an agent can. I dunno about AGI but this specific job is something that an LLM can already do better than every single human in the world. For me, as a systems engineer, having agents monitor my infra changes has been (no joke) more impactful in my day-to-day work than having agents write my code.
I started doing this many months ago by asking the agent to monitor explicitly after I triggered a deploy; soon after I moved to using a set of my own Skills. Now our Review Agents team has fully automated this workflow with delightful UX and obviously I'm not going back.
It's hard to overstate how powerful this is. All it takes, for me, in production:
- The Datadog MCP
- The PlanetScale MCP (for all our databases)
- Our custom MCP for deploys and internal tooling
That's it. Some carefully designed gradual deploy pipelines, and the agent just takes care of everything from there. You can't really deploy SEVs to production anymore.
Doing infra like this is pure joy. And the safety is just a tiny part of it. The Rollout agent also does the actually hard part of my job, which is _performance_.
When the changes you're deploying are a performance optimization, the agent prepares a monitoring plan that ensures the optimization is correct AND effective. I rarely prompt benchmarks for my optimizations anymore. Just fucking go to prod and the agent is gonna give me the best possible benchmark.
If you work on systems or infra for a living, you should be setting up your production environments so you can use Rollouts. Not doing so is actually reckless.
Josh Ferge retweeted
Introducing Rollouts.
Rollouts write a monitoring plan, then watch changes as they deploy.
Deployments are verified, so regressions are caught before users see them.
Josh Ferge retweeted
Grok Bot is now available to everyone with a standard Grok or Cursor subscription. It's grown faster than any product we've seen.
It's been particularly exciting to see the range of jobs people delegate to Grok Bot, from running small e-commerce businesses (including support, advertising, inventory, finance), coordinating customer events (directly pinging and working with dozens of human coworkers), testing production software, and completing large, mundane parts of users' day-to-day work.
my @bot helpers. still amazed at how incredibly delightful the experience is
🚀
Cursor is now part of @SpaceX.
Today, we have officially closed our acquisition. We will join the @spacexai team to help make Grok the world's most useful AI and improve Grok Build, Grok Bot, Grok API, Cursor, and more.
SpaceX has built some of the most inspiring and impressive technology in the world, and we’re grateful for the opportunity to become part of such a special company. Onwards.
I recently had my last day at @sentry. I learned so much and couldn’t have spent a better five years building great products with incredible people.
The journey continues at @cursor_ai (and soon SpaceX). I’m excited to help shape how software gets built in the years ahead. 🚀
You can now directly talk to @sentry in slack like Linear or any other agent. Give it a shot and let us know what you think



















