/graphify now on Computer. We're giving every user 5,000 credits to try this skill that lets you visualize a codebase.

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!

pstack v0.15.27 ships with a new skill /create-formal-verification-skill! it's still in beta, and similar to /create-verification-skill, this is a meta-skill that creates a new skill and formal verification suite based on the characteristics you want to verify. for example, you may want to model state machines and systems with concurrency using TLA+, or use kani in rust to check for undefined behavior. if you're new to formal verification, think of it as mathematically proving properties and invariants (something that must always be true) or "laws" of your system. usually, this means modeling your programs in a separate language like with TLA+ and then running the solver on that spec. newer approaches like with kani and @bendlang take a different approach where there is no separate language: you write kani in rust, and bend in bend (it's also a programming language, and the proofs are written as laws and expressed in its type system). historically formal verification never reached mainstream status because of the difficulty in modeling and writing proofs. it's quite difficult to model your business requirements and keep them in sync! but i expect that we will see more innovation in formal verification in the future as being able to formally verifiy that the code does what you intended gives your agents superpowers in writing correct software. in the meantime though, i've been experimenting with modeling our code with TLA+ and have already found several bugs with the skill created by /create-formal-verification-skill. try it out and let me know how it goes!

No pull requests, no code review. We push to main. Our agents read production logs, watch deploys, grant feature flags, and check their own work end to end. Here's how we do that:

I truly don't understand why nobody is using this setup graphify, a tool that turns any folder into a knowledge graph your agent can query, just passed 126k stars on github and got into Y Combinator. people stopped asking ai questions. they're giving it a desk, a memory and a job. you give Claude Code one folder, plug in your email, calendar and a browser, and it turns into an agent. it reads, remembers, acts, and checks itself before it does anything stupid. doesn't matter if you're a founder, a marketer or a student, you need this the full setup: > create a folder called AGENT, open Claude Code inside it and add a CLAUDE.md with one rule: "save every decision, person and project to memory/" > run npm install -g @googleworkspace/cli, then gws auth setup. now it reads your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser to open sites, fill forms and pull data for you > run uv tool install graphifyy, then graphify install, then type /graphify .. everything in the folder becomes a knowledge graph it queries in seconds instead of digging file by file > run npm i -g jev-guard, jev-guard key "...", jev-guard install claude. a tiny model called Jev scores every action before it runs. rm -rf gets blocked, a poisoned email gets flagged, for about 4 cents per 1,000 checks > type /schedule and tell it "every morning at 7:30, send me what came in, what you drafted and what waits for my yes". from now on it works on a routine 15 minutes to set up, and you never start from a blank chat again. every repo is below: -> github.com/googleworkspace/c… -> github.com/microsoft/playwri… -> github.com/Graphify-Labs/gra… -> github.com/leepokai/jev-guar… bookmark this

Remember when people said MCP was dead? We launched 6 weeks ago. Nearly 2M calls in September.