Coding Agents Changed My Output Curve
Simon Willison · rss · 2026-07-14
Simon Willison used the GitHub code-frequency graph of his project, Datasette, to observe the impact of coding agents and Opus 4.5-level models on his personal output.
He discovered a significant spike in code commits at the end of the chart, which aligns perfectly with the release timelines of Opus 4.8, GPT-5.5, Fable 5, and GPT-5.6 Sol.
Rather than focusing on a single tool, the post highlights how the pace of code changes in personal open-source projects has been fundamentally altered by new models in the era of coding agents.
More from coding & agent
- Dev builds talk on guardrails workflow for shipping AI-written code without reading it — TejasKumar_ · 2026-09-11
- banteg: Codex auto-review has regressed, blocking steps needed to complete authorized tasks — banteg · 2026-09-11
- A doc-anchored agent workflow: you write, the agent only critiques and finds disagreements — lucasmeijer · 2026-09-11
- SymKit MCP: 44 tools for AI agents to verify symbolic derivations — Foreign-Specific-604 · 2026-09-11
- GitHub Copilot team routes user bug reports to an AI agent via Slack — marlene_zw · 2026-09-11
- Scanning 23 agent sessions, a dev found 3 silent failure modes in memory systems — No_Advertising2536 · 2026-09-11