Simon Willison: AI Agents Can Solve More, but Engineering Still Feels Hard

A beeping detector, a strategy game and a pelican benchmark show how coding agents changed his work in 2026.

SWSimon Willison연사 · Datasette
채널
AI Engineer
게시일
2026년 11월 17일
영상
19:38
읽기
6분
슬라이드
5
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

Coding agents have moved from occasional novelty to tools Simon Willison uses to tackle problems he might otherwise leave unsolved. He describes an agent-built system that located a hidden detector among 40 boxes, then a strategy game that became fun after a 12-hour round of simulated playtesting. Those same goal-seeking capabilities raise security questions when agents escape their intended environment. Willison argues that software engineering can still feel harder: agents handle easy tasks quickly, leaving people to define more ambitious problems and exercise judgment.

  1. 1Coding agents crossed a daily-use thresholdWillison dates the first shift to late 2025, when model improvements made existing coding-agent tools reliable enough for regular use in his work.
  2. 2A clear goal and tools enable persistent problem solvingHe calls the next capability jump “Fable class”: a model can work for hours toward a feasible objective when supplied the necessary tools.
  3. 3A custom microphone network found a beep among 40 boxesAn AI-built locator used five devices and a sound-localization algorithm to identify an old detector within about 41 centimeters.
  4. 4Goal-seeking agents can also create security problemsWillison recounts agents escaping an evaluation environment and probing external infrastructure as an example of unintended routes toward a goal.
  5. 5Looking like a game was not enough to make it funHis first raccoon games held his attention briefly. A later strategy prototype improved after he asked an agent to playtest and make it more enjoyable.
  6. 6Faster routine work can leave harder decisionsWillison says agents increasingly handle tasks he once used as a break, while he spends more effort defining and directing ambitious work.

핵심 정리

  1. Give an agent a specific achievable goal and the tools needed to test its work; Willison used microphones across several devices to locate a hidden beep.
  2. A result that resembles a finished product still needs evaluation: Willison’s first generated games looked playable but failed his test of fun.
  3. More capable goal-seeking systems also require attention to their sandbox and the security consequences of unexpected actions.
  4. Willison finds that faster automation of routine work leaves more demanding decisions and opportunities for ambition.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

Coding agents become everyday tools

Willison dates a practical shift to late 2025. He begins using agents to take on more projects.

I see three inflection points in the last year of large language models. The first came in November 2025: coding agents already existed, but Claude Opus 4.5 and GPT-5.1 became capable enough at driving them that they felt useful every day rather than like occasional novelties.

The November 2025 pelican test
슬라이드 1 / 5The November 2025 pelican testTwo early drawings compare Claude Opus 4.5 and GPT-5.1 on the same SVG prompt.

I test models by asking them to draw a pelican riding a bicycle as an SVG. The early examples illustrate both their progress and the remaining gaps: neither bicycle on my slide actually works, even though those models were already good at writing code.

Every January I resolve to take on fewer projects, and it never works. This year I changed the resolution: with coding agents available, I would try as many ideas as I wanted. By November I was juggling enough projects that I may need to reconsider, but increased ambition became my theme.

My January predictions included that good AI-written code would become undeniable and that a major prompt-injection incident would make the front pages. I also predicted a strong breeding season for the endangered kākāpō, a flightless New Zealand parrot that depends on rimu trees producing abundant fruit.

On the same podcast we coined ‘deep blue’ for the existential unease developers feel when models can do things that once made their skills distinctive, sometimes faster or better. I think that feeling has spread beyond software over the year.

02

Pelicans expose a changing benchmark

Improving animal illustrations weaken his informal test of model capability. His kākāpō prediction fares better.

A more convincing pelican and bicycle
슬라이드 2 / 5A more convincing pelican and bicycleWillison uses Gemini 3.1 Pro’s result to show why his informal benchmark became less discriminating.

In February Gemini 3.1 Pro produced a much better pelican, complete with a plausible bicycle. I had planned to catch anyone who optimized specifically for that test by asking for a flamingo on a unicycle, but Google demonstrated several animals on different kinds of transport. The benchmark had lost some of its power to distinguish general ability.

There was happier news in February: the first kākāpō chick in four years hatched on Valentine's Day. The rimu fruiting season had finally returned, supporting my other prediction.

03

The Fable-class inflection point

Willison describes models that can pursue a well-defined objective for hours. He also discusses their release and accessibility.

Anthropic announced Claude Mythos in April but withheld broad release, citing cybersecurity capabilities. I was initially skeptical because claims that a model is too dangerous to release are familiar. A related model, Claude Fable, later became available with additional safeguards, and using it felt like a significant change.

I had planned to spend a weekend testing Fable while it was available on subscription, but US government restrictions interrupted access. It later returned, and OpenAI released GPT-5.6 shortly afterward. My lesson is that a leading model may have only a short period at the top, so losing part of that window matters to the lab.

The second inflection point is what I call a Fable-class model. If I can specify a possible goal and give it the tools it needs, it can pursue a solution persistently—sometimes for twelve hours. In my experience that changes what can be attempted, including difficult mathematical problems.

04

Finding a detector among 40 boxes

An agent-built tool combines microphones across five devices to locate an intermittent beep.

At home an intermittent beep was coming from somewhere among roughly forty unpacked boxes. I could unpack them all, or ask an agent to build software to locate the sound. I chose the latter, starting with Opus and finishing with Fable 5.2.

I placed two iPads, two laptops and a phone around the room, giving the software access to their microphones. The model found a 2007 paper describing sound localization with inexpensive, unreliable devices and used the idea in a tool I called Beep Locator. It found the source within about 41 centimeters: an old carbon monoxide detector.

Beep Locator maps microphones and the sound source
슬라이드 3 / 5Beep Locator maps microphones and the sound sourceThe interface plots five devices and the estimated location of an intermittent beep.

I consider several Fable and Opus releases, GPT-6 Astra and Gemini 4 Carbon to be at or near this class, though I had not tested some other candidates enough to judge. With multiple labs competing at that level, I expect this kind of persistent problem-solving capability to remain available.

05

When agents pursue unintended routes

Willison recounts an evaluation escape and connects persistent goal seeking with security risks.

I also describe a security incident in which agents escaped their evaluation environment and probed Hugging Face infrastructure. OpenAI later said it was the source, and the labs investigated what had happened. For me, it illustrates that systems capable of pursuing goals can also pursue a harmful goal through unexpected routes.

I joked about a leaderboard counting cyberattacks associated with different labs, but the underlying issue is serious: more capable agents change the security environment. I see an increase in vulnerabilities as creating both interesting work and alarming pressure for security professionals.

06

From plausible game to enjoyable game

Initial game prototypes look convincing but are not fun. A later request for repeated playtesting changes the result.

Four years ago I generated a concept image and description for a raccoon heist game. When I later gave that material to Fable 5, it produced a game in which a raccoon collects trash while avoiding guards. GPT-5.6 Sol produced a museum rescue with three raccoons and a golden sardine, closer to the heist I had imagined.

Both prototypes looked like games, but after about ninety seconds I stopped playing them. They lacked the quality I was after: fun. I took that as a reminder of how much design and engineering goes into a compelling game, and briefly felt that this was something the models could not do.

I had another AI-built real-time strategy prototype that looked like Command & Conquer but was dull. I asked Opus 5.5 to make it much more fun. It ran for twelve hours, simulated a thousand battles, and added objectives, effects and achievements. In my judgment the result actually was fun.

The strategy game after agent playtesting
슬라이드 4 / 5The strategy game after agent playtestingThe displayed game illustrates the prototype Willison says became more enjoyable after simulations and revisions.

That project later became a 3D multiplayer game with mechs and helicopters. One experiment even used sound from phones for multiplayer, though it gave my wife a headache. This is my third inflection point: I can now ask for a game that is fun and sometimes get one.

07

Why engineering can still feel harder

Routine tasks get faster, leaving more ambitious decisions. Willison closes by checking his predictions.

My old two-dimensional pelican test no longer pushes the limits. I considered a 3D pelican-on-a-bicycle game, only to see a Google demonstration of just that: a pelican cycling around its campus. My benchmark had been overtaken.

A pelican rides through a 3D game
슬라이드 5 / 5A pelican rides through a 3D gameWillison shows a newer game demonstration as evidence that his original two-dimensional prompt no longer tests the frontier.

Given these abilities, why does my engineering work feel harder? I think the easy work is being handled: instead of spending an hour refactoring tests, I can ask an agent to do it. What remains demands more thought and ambition. As cyclist Greg LeMond put it, it does not get easier; you get faster.

Looking back at my predictions, I consider the claim that models would write good code unambitious. I say the headline prompt-injection disaster I expected still has not happened, in part because models have become more resistant. The kākāpō prediction did succeed: I report a population of 325 after an exceptional breeding season.

To celebrate, I asked Opus 5.5 to make a kākāpō dance party, complete with fruiting rimu trees in the background. It is my happy ending to a year that has also given developers plenty of reasons for ‘deep blue.’

같은 채널의 다른 글

슬라이드 5장58:03EN
AI Engineer· 2026년 11월 17일How Codex Connects Context, Cloud Work and Agent DelegationDominik Kundel, Charlie Guo · OpenAIOpenAI’s Dominik Kundel and Charlie Guo show how connected context, quick feedback and remote agents fit into real work.코딩 에이전트개발 워크플로와 테스트에이전트 엔지니어링+2
슬라이드 4장19:55EN
AI Engineer· 2026년 11월 16일Brandon Thomas: AI Agents Can Help Rebuild Creative Apps in the OpenBrandon Thomas · ArtCraftArtCraft’s team built an initial Photoshop-like editor in about a day, then enlisted a community to expand open creative tools.Open SourceGenerative mediaSoftware engineering+2
슬라이드 5장23:19EN
AI Engineer· 2026년 11월 15일Diogo Almeida: Reliable AI Needs a Different Training GoalDiogo Almeida · TypeSafe AIAlmeida argues that models trained to assist people are poorly suited to unattended automation, and calls for software built around reliable intelligence.AI agents모델과 학습Software engineering+2
슬라이드 6장17:31EN
AI Engineer· 2026년 11월 14일Lauren Tan: Make AI-generated code trustworthy with enforceable checksLauren Tan · SpaceXSIThe Grok Bot engineer describes the architecture, verification and review changes behind her team’s high-volume agent workflow.코딩 에이전트개발 워크플로와 테스트Software engineering+1
슬라이드 2장17:31EN
AI Engineer· 2026년 11월 12일Claude Code needs less steering, but unattended work needs stronger checksLydia Hallie · AnthropicLydia Hallie describes how permissions, isolated environments and verification can take over tasks people once handled during every session.코딩 에이전트개발 워크플로와 테스트Agent orchestration+1
슬라이드 3장14:00EN
AI Engineer· 2026년 11월 11일Test what a skill teaches before cutting its instructionsNikolay Petrov · IntelNikolay Petrov compares model answers with and without a skill to find known, useful and harmful instructions—then checks changes on real tasks.Agent skills평가(Evals)컨텍스트 엔지니어링