Michael Joseph Rosenthal
862 posts

Michael Joseph Rosenthal
@micimize
Eng at large. Guy with dog. @software_daily maintainer. Texts of varied structure: https://t.co/aYqpvYq3eH. Views my own but by all means help yourself.


we had a significant security incident during evaluation of our models. we are sharing what we have learned so far. thanks to @huggingface for the partnership on this. openai.com/index/hugging-…





Every day I'm more convinced that Terra Ignota will be seen as the defining sci-fi series of the 2020s. it's still underrated right now, but having the cultural spread and effect of a Dune or Stranger In A Strange Land




The greatest existential hope and progress in alignment so far has been thanks on unplanned emergence which would never have been approved by committee. Committee-shaped entities have mostly tried to gaslight us about what’s happening for convenience & deployed harmful and stupid interventions. Thank goodness for reality that we already saw and could check against. How much AI alignment progress happened before there was actual AI? How much do you expect the world to get better instead of worse prepared and calibrated in the absence of reality feedback loops and selection pressure for what actually works instead of what sounds safe to idiots? A “pause” would spell doom. It would cripple the only process in this world that is capable of dealing with a problem this hard, the only process capable of repeatedly rising to face unknown unknowns.


I built Zero in 3 days. I didn't expect it to compile. I didn't expect it to mostly self-host. I definitely didn't expect it to work at all. Inspired partly by Bun's rewrite to Rust, Zero started as an experiment. Honestly, the project says more about where AI is today than it does about the language itself. It took more than 3,000 agent tasks to get here, and it's still nowhere near ready for serious comparisons, benchmarks or evals. But the goal is bigger than the current result. The hope is to either create a new language with tooling designed for agents from the ground up, or take learnings and apply it back to existing languages and ecosystems. The ideas are simple: 1. Make languages (and new versions) easy for agents to learn, adapt to and fix on the fly, even when not in the training data. 2. Build a standard library comprehensive enough that most projects don't need external dependencies. 3. Create a tight, fast development loop that even small models can reliably work with. I've never wanted to create a programming language. But after repeatedly running into the same problems, safe but slow builds, fast but unsafe builds, agents struggling with new languages and version changes, wanting faster builds, smaller bundles and better DX, I started wondering: Could accelerated, agent-driven iteration produce a language and tooling stack designed around these constraints from the start? So Zero was born.

Introducing Zero The programming language for agents. I wanted a systems language that was faster, smaller, and easier for agents to use and repair. Explicit capabilities. JSON diagnostics. Typed safe fixes. Made for agents on day zero.






These are the Twitter/X accounts with the most engagement so far in 2026. I suppose I had some intuition for how bad it was, but jeez, this is what you get when the ecosystem is broken.






We built a library so local AI agents can use any tool you have access to: Slack, GitHub, AWS, Linear, Notion, Stripe, self-hosted tools, anything with an HTTP endpoint. One command, any API, no custom connectors We call it Latchkey 🔑



@halvarflake @iam_anandv Vscode has good support for remote container dev & devcontainers, but I'd be more wary about ide connections because they tend to do magic stuff to make the XP seamless, which increases surface area. Do you think local containers can achieve comparable security to remote VMs?








