4 stories
The big editors all have an agent built in now, and each of them has added a way to look at what the agent did before you keep it. I build Reado, the IDE for reading the code your agent writes, so I have an obvious interest in this question.
Claude Code helped Linus Torvalds explore a Linux memory-management change, write test programs and draft its explanation. The interesting part is in the cover letter: an experimental patch series reduces the cost of a particular shared-file workload, makes another read path slower and leaves…
When an AI agent hands you a diff, reading it line by line is the last step, not the first. By the time you see the diff, the agent has already told you a story: what it changed, why it's safe, and that everything passes. A senior review checks that story against evidence.
Limits, before anything else. 21 attempts on one defect are repeated observations, not 21 independent tests. One seeded bug: an inverted authorization check in material I wrote myself. Run on 21 August 2026. One small local model. The alias local-advisor-v1:latest is local.
Showing 4 of 4 stories
You're all caught up.
Get the top AI news and tools straight to your inbox every week.
Weekly · AI news from Dev.to AI
Join 15,000+ AI enthusiasts
