Ittai Zeidman

Last night an AI agent performed brain surgery on a mouse. We gave it 19 gene therapy vectors in a spreadsheet, a mouse model of epilepsy, access to a motorize surgery rig with cameras and one goal: reduce seizures. It picked the drug. It picked the brain region. It derived the coordinates from three papers. Then it drove the stereotaxic arms into the brain and injected 250 nanolitres while watching the entry site through the rig camera for bleeding. A licensed vet gated every irreversible step and held a physical kill switch to stop the AI agent. Thread on what it decided, what it saw, and the moment it refused to let me override it. [Writing this on the spot out of excitement, but I've been 18hrs in front of my laptop coding and coordinating this, so keeping it brief and descriptive, more cohesive thoughts on this soon...]

What does it take to build agentic products on open-weight models? @ittaiz is speaking at @NVIDIA GTC Berlin 2026! 👏 He'll join a panel exploring why builders are moving to open-weight models, the trade-offs in cost, latency, and quality, and what it takes to run them safely at scale - including what stays on closed models and why. Good luck, Ittai!

Today we’re introducing Base Code. It’s an early preview of how we think software will be built in the future. It’s a product that encapsulates everything we’ve learnt from: - How our users are building software. - How we’re building internally, scaling to hundreds of millions of dollars in revenue while keeping our engineering team very small and focused. Here are some of the principles behind it, which align with how we at @Base44 think about the future of software engineering: Cloud: - Software will move past local desktop environments (where current tools are widely used) and move to the cloud. - Moving everything to the cloud is not easy. Setting up dev environments with databases, infra components, services, mock data, etc. is easier said than done. - Base Code first scans your code repo and sets up everything - every infra component (databases, Redis, etc.) - in the cloud. It runs nonstop until your preview environment is ready. - From an enterprise standpoint, it’s also the logical thing to do: a centralized, governed dev environment instead of handing out keys and secrets to all team members. - Once Base Code does that, EVERY team member can work in this environment. No more syncing local environments. Internally, this (cloud) is one of the main things that enabled us to move so fast. Collaboration: - Once everything is in the cloud, everybody can write software from anywhere (any browser, your phone, WhatsApp / iMessage coming soon). - You can easily see what everyone is working on, where they’re at, and how they’re prompting - and jump to their environment in one click. - We’ve built many great collaboration features from the ground up. Loops, automations, software factories: - A full, working cloud environment allows for many advanced capabilities we will unveil soon-think agents running in the browser and testing on every device and in any browser. - It also allows the use of automations to build software factories-e.g., agents reading support tickets, identifying bugs to fix or features to develop, implementing the changes, verifying them in the cloud, and potentially pushing them. And lastly, there’s a real advantage in being model agnostic. -------------- As always, we’re releasing it very early. It’s far from perfect-but we’re looking for early feedback so we can build it together with our great community and make this vision a reality. *We’re giving it away for free for 30 days*. Give Base Code a try. Connect any GitHub repo, get your live preview, and share it with your team. I’d love to hear what works and what doesn’t: app.base44.com/base-code