How do you _guarantee_ your agent's code is correct? You prove it.
Introducing Proof Driven Development Kit (PDD Kit) from @MSFTResearch.
PDD Kit helps turn your plan into a formal spec, then proves the agent's code meets that spec for every input. No vibe verification. PDD Kit is integrated with @GitHubNext's Chopin, so you can plan as a team.
PDD Kit takes an app's login flow from intent to a verified pull request:
It discusses your code, infers your intent as it goes, and proposes a formal spec in Verus, a proof language for Rust.
Once you approve the spec, the Verus verifier automatically proves the code meets it.
Where proof isn't possible, it falls back to empirical verification with tests and computer-use agents (CUAs).
It works on Rust today. No new language, no change in how you produce the underlying code, making formal methods more accessible.
The goal is a verified software factory, where engineers review specifications instead of code.
Come see it in action at GitHub Universe, Oct 28–29. Swing by the Speakeasy and ask for GitHub Next!
@MrPeterLMorris Verus exists for Rust today. If we can prove this out (and build a good experience around it) then that will probably lead to verifiers for more languages. This isn't about rust vs other languages, it's about making it work well and then taking the learnings to every other lang
So much is moving towards computers becoming actual terminals again, running their compute *somewhere else*. Even the personal stuff.
The Hypercloud Movement™
How do you solve the trust problem with AI-generated code?
AI agents can generate code at a scale too great for humans to review line-by-line. That makes it difficult to ensure the code will do what the developer intended, and it leaves the final output vulnerable to bugs and security risks.
Proof-Driven Development Kit turns plain-language developer intent into a specification in Verus, applying formal methods traditionally used for safety-critical systems. PDD Kit uses mathematical proofs to test agent-generated code against the spec where possible, and clearly indicates where the proofs can’t reach. The result is more reliable agentic code.
Researchers @MatthaiP39719 and @alexlavaee break down Proof-Driven Development in the MSR blog: https://t.co/PoNqwr9EOk
Making 50% of the world’s code verifiably secure.
Traditionally, formal methods have been relegated to verifying safety-critical systems like operating systems, hypervisors, databases, etc. We��re extending this approach to formally and empirically verify code correctness and security for full-stack web applications using Proof-Driven Development Kit (PDD Kit).
A large portion of the world’s software consists of web applications, and we see this as a starting point for our everyday software.
Check out our blog here: https://t.co/C6RZdJFPmh
From @GitHubNext x @MSFTResearch
We've just published an in-depth write-up about the PDD Kit - collaboration project between us (@GitHubNext) and @MSFTResearch focused on formal verification in the world of AI agents. 🤖
Check it out:
https://t.co/ulOF50DCPk
How we can secure 50% of the world's software.
Traditionally, formal methods have been mostly used for safety-critical systems like operating systems, hypervisors, and databases. We're extending this to formally and empirically verify code correctness and security for full-stack web apps, one of the most common types of applications*, using the Proof-Driven Development Kit (PDD Kit).
Coding agents now write code faster than anyone can review effectively. PDD Kit turns what the developer meant into a Verus specification. It then proves the AI-generated code meets that spec for every input.
Researchers @alexlavaee, @MatthaiP39719, @Mappletons, and @k_cieslak break down Proof-Driven Development x Chopin in the blog here: https://t.co/EwhqTx2OjT
*44.4% of respondents work as full-stack (27.3%), back-end (13.5%), or front-end (3.6%) developers. Stack Overflow Developer Survey 2026, n = 25,767.
GitHub Agentic Workflows has graduated out of the lab and is now generally available! We're excited to see more projects and businesses leverage AW to automate the things that could not be automated before AI.
https://t.co/RVXDoI8WC4
Missed the closing keynote at GitHub Universe? You can see @Mappletons from GitHub Next demoing Chopin, our exploration of multiplayer planning for the agentic era
https://t.co/gwoD15qvd3
Furiously making last minute preparations for our talk tomorrow, here's a fun mixtape from the Next team to jam to during @githubuniverse!
https://t.co/F9VULoX8Ma
A new project from GitHub Next!
Chopin is a real-time, multiplayer agentic planning environment. Designed to get your whole team aligned on the plan before you hand it off to agents.
We find our current agent planning tools feel cumbersome, static, lonely, and drown us in walls of text. We're exploring how we can make planning more interactive, shared, and visual 🖌️
It's currently an early prototype but we'll be developing it more over the coming months – and it's open source!
https://t.co/in190YYgh7
Unfortunately not :(
We are sad about it as well. The infrastructure required for Ace was complex and we're currently unable to ship a secure, production-ready version of it with just our tiny team. GitHub rightly has engineers focused on more important issues.
But we are trying to keep the spirit of Ace alive in Chopin, bringing in a lot of our ideas about multiplayer, real-time collaboration, proactive agents, and team visibility of decisions and context.
Today is my first day at @GitHubNext!
GitHub has been one of my favorite places to hang since I signed up 18 years ago(!), a mere month after its founding.
Excited to join this talented team to try and figure out what comes next for our craft ...
🇯🇵 In Japan? Idan Gazit from @GitHubNext and @JasonEtco from the @github Copilot team will be speaking at @findy_tools AI Engineering Summit on December 14+15. ✨
Found time last week to cleanup the homepage & docs of Agentic Workflows, one of the very successful @GitHubNext projects of the last year. TLDR: run your own software factories on GitHub Actions
Previous page was vibed by agents and backend developers. Took me a day to redo it.
Had a wonderful chat with @GergelyOrosz - always nice to go deep on ideas in a proper long chat. Got to show off some notebook sketches and design jigs with agents too.