korrents
Simon Willison

What Simon Willison thinks about coding agents

@simon-willison · 57 positions · On ppll ↗

Co-creator of Django and creator of Datasette; writes daily at simonwillison.net.

Simon Willison did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

12 dated positions, 2025 to 2026, in their own words. Our reading of what Simon Willison has said — not written or endorsed by them.

  1. These two new models, when paired with their respective coding agent harnesses, improved from “often make mistakes” to “reliable enough to use on a day-to-day basis”.

    ↗2026 in LLMs (so far)simonwillison.net

  2. 3 days earlier
  3. The more time I spend working with coding agents, the more convinced I am that they make software engineering even harder.

    ↗Note on 24th September 2026simonwillison.net

  4. 12 days earlier
  5. OpenAIdesign

    Frustratingly, the actual code it ran and exact details of what it did weren’t visible to me in the ChatGPT UI. I see this lack of transparency is an anti-feature.

    ↗Generating running routes with GPT-6 Astra and ChatGPT Worksimonwillison.net

  6. 5 weeks earlier
  7. prompt injection

    I REALLY want to believe that this fixes prompt injection risks for coding agents, but I'm just not there yet

    ↗@simonw on Xx.com

  8. 5 months earlier
  9. it turns out you can do this if you think really hard about okay, how do I have agents prove to me that the stuff they've written works?

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 1st of 18 in this recording

  10. the key thing about TDD is that it means that the agents won't write more than they need to.

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 3rd of 18 in this recording

  11. I think I see people who are writing code with coding agents and they're not writing any tests at all. That's a terrible idea.

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 4th of 18 in this recording

  12. one of the magic tricks about these things is that they they're incredibly consistent. If you've got a code base with a bunch of patterns in, they will follow those patterns almost to a T.

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 8th of 18 in this recording

  13. So, I think the most important thing is sandboxing. You want your coding agent running in an environment where if something goes completely wrong, if somebody gets malicious instructions to it, that the damage is greatly limited.

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 12th of 18 in this recording

  14. I think that might be what saves us. I think the fact that no, you can't have one engineer and have him do a thousand projects because after three hours of that he's going to literally pass out in a corner.

    ↗Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summityoutube.com 15th of 18 in this recording

  15. 3 months earlier
  16. MCP

    The reason I think MCP may be a one-year wonder is the stratospheric growth of coding agents. It appears that the best possible tool for any situation is Bash—if your agent can run arbitrary shell commands, it can do anything that can be done by typing commands into a terminal.

    ↗2025: The year in LLMssimonwillison.net

  17. I run in YOLO mode all the time, despite being deeply aware of the risks involved. It hasn’t burned me yet... ... and that’s the problem.

    ↗2025: The year in LLMssimonwillison.net