I love this term AI “slop grenades”
I’ve been talking about this a lot without a good name for it, but this makes sense!
This is a problem plaguing companies right now, don’t let it be you or your team!
Lazy work used to mean too little output.
Now, with AI, it often means too much and more work for everyone else.
@tobi call it "slop grenades."
A "Slop Grenade" is when you let AI produce the work and pass it on without adding any value (including checking it).
Someone else has to wade through it, catch the mistakes, and clean up the mess.
You save time and look productive but someone else pays for it.
1
1
169
Bobby retweeted
We're shipping a new feature in Claude Cowork as a research preview that I'm excited about: Dispatch!
One persistent conversation with Claude that runs on your computer. Message it from your phone. Come back to finished work.
To try it out, download Claude Desktop, then pair your phone.
Bobby retweeted
Introducing the new /crawl endpoint - one API call and an entire site crawled.
No scripts. No browser management. Just the content in HTML, Markdown, or JSON.
LETS GOO
The best image model just got an upgrade - Nano Banana 2
so excited for this, it benefits so many workflows for visualizing things
Introducing Nano Banana 2: Our best image generation and editing model yet. 🍌
Pro-level quality, at Flash speed. Rolling out today across @GeminiApp, Search, and our developer and creativity tools.
The future is starting to materialize
Talk to a real-time avatar that seems like a real person.
They're so close to crossing that uncanny valley.
Introducing Phoenix-4, the most advanced real-time human rendering model ever built.
Its the first real-time model to render every pixel at runtime, generate and control emotional states, listen actively, and actually behave the way humans do in conversation.
1
3
487
BREAKING OPENCLAW NEWS:
@steipete Joining the @OpenAI team
"We expect this will quickly become core to our product offerings."
"OpenClaw will live in a foundation as an open source project that OpenAI will continue to support."
More Info: steipete.me/posts/2026/openc…
Peter Steinberger is joining OpenAI to drive the next generation of personal agents. He is a genius with a lot of amazing ideas about the future of very smart agents interacting with each other to do very useful things for people. We expect this will quickly become core to our product offerings.
OpenClaw will live in a foundation as an open source project that OpenAI will continue to support. The future is going to be extremely multi-agent and it's important to us to support open source as part of that.
I think ElevenLabs just solved the uncanny valley for AI call agents.
You need to try the new Expressive Mode 🔥🔥🔥
GPT 5.3 Codex is now in Cursor!!
Its that time again to go press all the model toggles
Hey @cursor_ai @ericzakariasson @leerob can yall make this less annoying to pick the newest openai model variants?
1
4
624
I’m so glad I started diving into AI tools for code in 2024 so I have a proper timeline understanding as things shift at ludicrous speeds.
If you haven’t committed to using AI for development, the time is now.
From simple tab autocomplete to full yolo agents in like 2 years 🚀
Software development is undergoing a renaissance in front of our eyes.
If you haven't used the tools recently, you likely are underestimating what you're missing. Since December, there's been a step function improvement in what tools like Codex can do. Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging. Not everyone has yet made that leap, but it's usually because of factors besides the capability of the model.
Every company faces the same opportunity now, and navigating it well — just like with cloud computing or the Internet — requires careful thought. This post shares how OpenAI is currently approaching retooling our teams towards agentic software development. We're still learning and iterating, but here's how we're thinking about it right now:
As a first step, by March 31st, we're aiming that:
(1) For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal.
(2) The default way humans utilize agents is explicitly evaluated as safe, but also productive enough that most workflows do not need additional permissions.
In order to get there, here's what we recommended to the team a few weeks ago:
1. Take the time to try out the tools. The tools do sell themselves — many people have had amazing experiences with 5.2 in Codex, after having churned from codex web a few months ago. But many people are also so busy they haven't had a chance to try Codex yet or got stuck thinking "is there any way it could do X" rather than just trying.
- Designate an "agents captain" for your team — the primary person responsible for thinking about how agents can be brought into the teams' workflow.
- Share experiences or questions in a few designated internal channels
- Take a day for a company-wide Codex hackathon
2. Create skills and AGENTS[.md].
- Create and maintain an AGENTS[.md] for any project you work on; update the AGENTS[.md] whenever the agent does something wrong or struggles with a task.
- Write skills for anything that you get Codex to do, and commit it to the skills directory in a shared repository
3. Inventory and make accessible any internal tools.
- Maintain a list of tools that your team relies on, and make sure someone takes point on making it agent-accessible (such as via a CLI or MCP server).
4. Structure codebases to be agent-first. With the models changing so fast, this is still somewhat untrodden ground, and will require some exploration.
- Write tests which are quick to run, and create high-quality interfaces between components.
5. Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high
- Ensure that some human is accountable for any code that gets merged. As a code reviewer, maintain at least the same bar as you would for human-written code, and make sure the author understands what they're submitting.
6. Work on basic infra. There's a lot of room for everyone to build basic infrastructure, which can be guided by internal user feedback. The core tools are getting a lot better and more usable, but there's a lot of infrastructure that currently go around the tools, such as observability, tracking not just the committed code but the agent trajectories that led to them, and central management of the tools that agents are able to use.
Overall, adopting tools like Codex is not just a technical but also a deep cultural change, with a lot of downstream implications to figure out. We encourage every manager to drive this with their team, and to think through other action items — for example, per item 5 above, what else can prevent a lot of "functionally-correct but poorly-maintainable code" from creeping into codebases.
1
189
AI video is 1 or 2 model updates away from being undetectable between real or AI
its crazy how much its improved in just a year.
Once it reaches the quality peak, then all it needs to do is get cheaper
Kling 3.0 is truly "one giant leap for AI video generation"! Check out this amazing mockumentary from Kling AI Creative Partner Simon Meyer!
1
195



















