@mattpocockuk https://t.co/tR0coQIHFN
I’ve been exploring a similar problem with SOAP, a skill for reviewing friction in human–AI development sessions.
Reading retro gave me some ideas to bring into SOAP—especially choosing automated checks over adding more instructions. Thanks for sharing!
https://t.co/sRyO7OigQ7 is our new home for developers building with Claude.
You'll find engineering deep dives, Claude Code and API guides, tips from the teams building Claude, and some fun easter eggs.
Meet Berd
We just dropped the best way to run your favorite models + agents in one interface.
Open source.
Super clean UI.
Gloopies.
Like Codex, but more vibey. Give it a try. I love it.
https://t.co/wsgs7j393F
Origin, our code hosting platform, is now live.
It's fast, easy to use, and deeply integrated with Cursor.
Get started by syncing your repos from GitHub.
Introducing Grok Bot, now in early beta.
Bots are AI teammates that do real work for you. They sign in to your tools, use them just like you do, and come back with finished work.
Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing.
Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan.
This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night.
How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget").
This means two things, both of which I think are Big Deals:
1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app.
2. Since everyone is running their own copy of the code, everyone can freely *modify* their copy of the code.
Think about #2 a bit more.
What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it?
This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app.
Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget.
And it is so fun.
https://t.co/qzwdrAQhtK