Harness Self-Evolution Needs to Retro Its Own Retro Changes
mattpocockuk · x · 2026-11-03
Matt Pocock quotes a paper on agent harness self-evolution: generating and implementing changes isn't enough — you need ways to establish whether a change helps on later tasks, and to revise or remove changes that don't. His takeaway: "we need to /retro whether our /retro changes actually made a difference."
Related event: Paper Evaluates Matt Pocock's /retro Skill(2 posts)→
More from coding & agent
- Dev open-sources faster-chrome-devtools-skill after analyzing 2,500 agent uses — simpsoka · 2026-11-03
- Shipping an enterprise project with Claude and Codex: AI writes, judge scores, you decide — kmeanskaran · 2026-11-03
- Neo4j GraphRAG Python package defaults to CPU-only PyTorch wheels to cut install overhead — JeremyCMorgan · 2026-11-03
- Zero-dependency SQLite + FTS5 MCP server adds persistent memory and anti-loop tracking to coding agents — AvocadoJaded8829 · 2026-11-03
- Developer says Kimi's $40 coding plan burned 3% of monthly usage reading one project guideline — Chaosuka · 2026-11-03
- OmniMem gives coding agents persistent memory of dead ends, hits 12k downloads — Ancient_Ad8787 · 2026-11-03