Every Correction You Give Your Agent Is Data - Brian Douglas, Paper Compute @aiDotEngineer
Every Correction You Give Your Agent Is Data - Brian Douglas, Paper Compute  @aiDotEngineer
Uploaded November 2026 | Updated November 2026, 5 days ago
A Rust program can compile and still violate the decisions an experienced teammate would catch immediately. Brian Douglas finds that missing knowledge in moments when engineers push back on their coding agents. At Paper Compute, he captures agent sessions, labels corrections and uses those traces to recover the reasoning that otherwise disappears inside a local coding harness. His example starts with a gap in his own Rust expertise: accepting plausible generated code leads to objections later, when a teammate reviews the pull request. Those earlier objections become useful training material only if someone preserves and labels them.

Brian demonstrates session capture with Tapes and Paper Console, then runs a Twin Review prototype against a pull request using examples of a teammate's feedback. He discusses labels for pushback, successful sessions and regressions, and shows how the same records can support skills, evaluations or model adaptation. The prototype is a demonstration, not a measured comparison against an independent evaluation set, and Brian corrects himself during the recording to clarify that Twin Review is not publicly released because its data is sensitive. His practical starting point is simpler than training a model: collect the traces you already generate, find the corrections that encode your team's conventions, and turn those into a skill you can test. The durable asset is the connection between a decision, the expert's objection and the resulting outcome.


Speaker info:
Brian Douglas, Paper Compute
- https://b.dougie.dev/
- briandouglas.me
- https://tapes.dev/

Timestamps:
0:00 - Engineering judgment and agent feedback
1:47 - Capturing sessions with Tapes
3:43 - Labeling expert pushback in Paper Console
5:59 - Turning traces into a review dataset
6:28 - The Twin Review prototype
8:06 - Useful labels and recurring failure patterns
9:32 - Start with skills and evaluations
10:48 - Model adaptation experiments and closing advice
Every Correction You Give Your Agent Is Data - Brian Douglas, Paper ComputeRethinking Claude Code Best Practices — Lydia Hallie, AnthropicBuilding Agents with Amazon Nova Act and MCP - DuAn Lightfoot, Amazon (Full Workshop)Catch the Bugs Your Code Review Misses - Killian Carlsen-Phelan & Taylor Luttrell-Williams, SonarEngineering Agency out of the Happy Path — Matthew Jewkes, Standard CyberneticsYour Agent Is a Lethal Trifecta (And What to Do About It) — Kim Maida, KeycardExploits Now Beat Patches: Open Source Security in the AI Era - Patrick Smyth, ChainguardThe Base Model Is Dead — Varun Singh, Arcee AIHow Evals and Prompts Shape Agent Behavior — Preetika Bhateja & Daniel Bump, YouTube AdsWhy AI Wont Replace Stock Pickers - Jack Woodruff, Candlestick & Vinoo Ganesh, KeplerAIE CODE: Google DeepMind, OpenAI, ArtCraft, Cognition, Exa, Anthropic, Amp, et alWhen we can do anything, do we still know what we want? — Ryo Lu
AI Engineer |

Every Correction You Give Your Agent Is Data - Brian Douglas, Paper Compute

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER