Dagens Vibes — 4. oktober 2026

THE RECIPE https://t.co/1oezv7fqg1 Ask your agent to build this and ENJOY FREEDOM 🥳

We spent the last week building with @VictorTaelin’s @bendlang on real projects, and came away pretty impressed. Some takeaways: 1. Bend changes what the human needs to pay attention to. Instead of reviewing every implementation detail, you can spend more time getting the intent and laws right, then let the agent figure out the implementation and proof. You still need to make sure the laws actually express what you want. 2. Agents make formal verification much more practical. The annoying part used to be writing and maintaining the proofs. Now the agent can do that work. Basically: you don’t need deep math knowledge to start anymore; you can work through the problem in English and use the model to find the algebra/laws. 3. The proof is useful feedback for the agent, not just a safety certificate at the end. This was probably the most interesting thing we actually observed. In one of our projects using Bend, the agent proposed roughly 20 laws. When we made it prove all of them, 4 of the original laws were actually false. The proving process found counterexamples, forced the edge cases to be stated correctly, and changed the implementation. 4. Bend being a real general-purpose programming language with formal verification built-in matters a lot. Before Bend 2 existed, you might have your real program in Rust/TypeScript and separately model it in Lean/TLA+. Then you have to trust that the thing you proved still matches the real program. Bend lets the code you execute also be the thing whose laws you prove. No more worrying about the 'model of your code' drifting from the real code. 5. You probably shouldn’t formally prove everything. This was an important conclusion for us. Use it where correctness really matters, where the logic has a clear mathematical shape, where agents keep tripping up, or where there's a core that will evolve a lot. Proving every trivial piece of an app can be overkill and costs more tokens/time. 6. You don’t have to rewrite your whole app in Bend to use it. It's easy to get started. We took one correctness-critical part of one of our existing TypeScript projects, rewrote just that slice in Bend, compiled it to JavaScript, and left the rest of the application alone. It is now 100% bug-free (actually proven!) and 4x faster. We recorded our whole journey trying out Bend 2: 00:00 A new verification layer 00:47 Machine-checkable guardrails 10:11 Types, tests, and proofs 17:49 Find a problem worth proving 20:30 How algebraic laws enable optimization 25:03 Find the algebra 30:38 From exploration to self-contained spec 32:20 Laws that reflect your intent 37:33 Proofs and false laws 42:12 Bend in one part of an existing project 45:55 Costs and how much to prove

well, this works better than Claude for Android or ChatGPT for Android has ever worked. It runs on my phone directly, no cloud vm. I can live edit it. Its multiplayer. And I can pick any provider/model. Just added artifacts. There is no moat. 24h of slop, developed on the phone, on top of Pi Durable :)

everyone thinks codex computer use only works inside codex it doesn't, it's a local mcp server in the chatgpt mac app and claude code can just call it, even headless with claude -p same 8-task test: opus 5.5 on codex's engine got 6/8, codex itself got 6/8, cua driver got 3-4/8 at 4x the cost cua's background mode on mac only goes through accessibility, so canvases and drags just don't land codex's engine sends real clicks and drags to the app without touching my cursor no hover though, and it's unofficial, so enjoy it until a chatgpt update breaks it give this to your claude: "Set up Codex's computer use as an MCP server for you on my Mac. Find the "cua_repl" entry in ~/.codex/plugins/cache/openai-bundled/unified-computer-use/<newest version>/.mcp.json and register it as a user MCP server called "codex-cu" with the same command, args and env. Then test it by using Calculator in the background to work out 12 × 12."

I mixed Jev + an espresso (state) machine. Turns out, Jev's a pretty good barista ☕ Introducing Jevspresso: XState determines what's possible, Jev decides the next move. Order in plain language, or break stuff and watch Jev cope. Try it: https://t.co/5362t1EyZV https://t.co/h5tbbMW7z5

Shareware model still works in 2026 https://t.co/i3hi2ln9cP