Quinten Farmer

x.com/i/article/2032…

I vibe coded a new product on the side while running @every—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at proofeditor.ai. Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof @every: - @bran_don_gell had @OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - @tedescau texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using @naveennaidu_m's @usemonologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - @kieranklaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on @every's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

x.com/i/article/2028…

I'm extremely excited to announce that we've successfully inferenced π0.5 on our excavator! We've collected a massive corpus of real-world data with natural language labels from operators in the industry and are using it to create some really cool policies. Here's our first demo of it successfully completing a task with just 200 trajectories. More on the way :) Read our blog post: labs.actor/research/vla-e… @physical_int

Awesome job by the @databricks team My summary: They trained a model called KARL that beats Claude 4.6 and GPT 5.2 on enterprise knowledge tasks (searching docs, cross-referencing info, answering questions over internal data), at ~33% lower cost and ~47% lower latency. The key insight: instead of throwing expensive frontier models at enterprise search, you can use reinforcement learning on synthetic data to train a smaller model that's faster, cheaper, AND better at the specific task. RL went beyond making the model more accurate. I t learned to search more efficiently (fewer wasted queries, better knowing when to stop searching and commit to an answer). They're opening this RL pipeline to Databricks customers so they can build their own custom RL-optimized agents for high-volume workloads. I think we'll continue to see data platforms become agent platforms. Databricks' KARL paper is really an agent platform play. The pitch: you already store your enterprise data in the Lakehouse, now Databricks will train a custom RL agent that searches and reasons over it, tuned specifically for your highest-volume workloads (workloads = apps = agents). The business move is closing the loop: data storage → retrieval → custom agent training → serving, all on Databricks. They're turning "your data lives here" into "your agents live here too." Kudos @alighodsi @matei_zaharia @rxin