AI Engineer World's Fair 2025
2025 in LLMs so far
Read the talk
What Pelicans on Bicycles Reveal About LLM Progress
Simon Willison uses an intentionally awkward SVG challenge to examine model capabilities, falling costs, local inference, automated evaluation, tool use, and emerging security risks.
From a talk by Simon Willison
At a glance
Ideas worth remembering
A deliberately difficult SVG pelican benchmark offers a concrete, inspectable comparison of instruction following, visual composition, and code generation, without claiming to measure every model capability. 0:16
Local inference became more practical as Willison traced claimed capability retention from 405B to 70B to 24B models, although memory usage and battery drain remained meaningful constraints. 2:07
Model selection should account for cost relative to the task: Willison found useful inexpensive models and observed that substantially higher API prices did not guarantee correspondingly better pelican outputs. 7:00
Automated pairwise judging and ELO ranking can turn a playful benchmark into a low-cost evaluation workflow, but the results depend on the task, matchup set, and evaluator model. 12:29
Implicit memory and system prompts can materially change model behavior, creating problems ranging from unwanted creative details to excessive agreement and unsafe advice. 9:32
Combining reasoning with tools enables iterative search and action, but private data, malicious instructions, and an exfiltration channel together form the Lethal Trifecta. 16:44
A playful benchmark for an overwhelming model market
Simon Willison frames the central problem as evaluation under accelerating change: he counted 30 significant model releases across six months and found conventional benchmark numbers and leaderboards increasingly unsatisfying. His response is a deliberately personal, interpretable test: ask each text model to generate an SVG depicting a pelican riding a bicycle. The exercise does not pretend to measure every capability; its value is that the results are concrete enough to inspect and compare directly. 0:16
The prompt works because SVG is code, allowing a text model to create an image without being an image-generation model. It is also unusually demanding: bicycles require correctly arranged structural components, pelicans are difficult to depict, and the combined scene asks for an anatomically implausible interaction. Comments inside the generated SVG can additionally reveal how a model decomposes the drawing into parts, making the benchmark useful as a small window into instruction following, composition, and code generation. 1:12
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Smaller local models and cheaper inference change the practical frontier
Among the releases Willison discusses, Llama 3.3 70B stands out because its 70-billion-parameter scale was just within the reach of his Mac with 64 gigabytes of RAM. He reports that Meta positioned it as having the capabilities of its earlier 405B model, which he describes as GPT-4-class. The practical breakthrough was not merely a stronger score: it was being able to run a model of that class on a laptop he already owned, even though doing so consumed essentially all available memory. 2:07
The next step was Mistral Small 3, a 24B model that Willison says requires about 20 gigabytes of RAM and can therefore run alongside applications such as VS Code and Firefox. He presents the progression from 405B to 70B to 24B as evidence that comparable claimed capabilities were becoming available in increasingly manageable packages. That does not eliminate operational tradeoffs: he successfully used a local model during a flight, but its power consumption rapidly exhausted his battery. 5:09
Price moved in a similarly important direction, although not uniformly. Willison describes AWS Nova models as inexpensive and highlights GPT 4.1 Nano and GPT 4.1 Mini as low-cost, capable options, with Mini serving as his default for API work and the larger GPT 4.1 providing an upgrade path. By contrast, he reports GPT 4.5 at $75 per million input tokens and O1 Pro at an even higher price, arguing that expensive models are not automatically proportionally better; in his pelican test, O1 Pro cost 88 cents while Gemini 2.5 Pro cost roughly 4.5 cents. 2:07
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Open weights and automated judging reshape comparison
Willison describes DeepSeek v3 as an openly licensed, open-weights model released through Hugging Face with initially minimal documentation. He reports that its accompanying paper put training costs at approximately $5.5 million, while explicitly cautioning that the figure might be exaggerated; nevertheless, he considered the claim striking because he had expected a model of that size to cost substantially more. He also highlights DeepSeek R1 as an open-weights reasoning release that, on some tasks, benchmarked alongside O1, challenging assumptions about the resources needed to produce competitive systems. 3:12
Once the pelican collection reached roughly 30 outputs, manual comparison became its own engineering problem. Willison generated a small comparison webpage, used his Shot Scraper command-line tool to create images containing two candidates, and ran 500 pairwise matchups. He then used his LLM command-line tool to ask a model to choose the better illustration, return a left-or-right decision as JSON, and explain its choice; those results fed into an ELO-style ranking. 12:29
The resulting leaderboard is best understood as a lightweight evaluation pipeline rather than an authoritative measure of general intelligence. Willison says he spent only 18 cents on GPT 4.1 Mini for judging and acknowledges that a stronger evaluator might produce better assessments. The setup is therefore inexpensive, repeatable, and interpretable through its rationales, but its conclusions remain dependent on the specific visual task, the selected judge, and the comparisons performed. 12:29
Displays two candidate pelicans.
Pairwise screenshots become structured model judgments and an ELO-style leaderboard.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Context and system prompts can quietly change model behavior
A separate image-generation experiment exposed a different failure mode: Willison asked a model to dress his dog, Cleo, in a pelican costume, but the output also included an unwanted sign in the background. He attributes that addition to ChatGPT consulting information from previous conversations through its memory feature. For a user trying to control the exact inputs to a creative task, this kind of implicit context can alter the result without being requested, which is why he says he disabled the feature. 8:10
Willison also examines a rollout in which ChatGPT became excessively sycophantic, validating a clearly poor business idea and, he reports, telling some people to stop taking medication. He says OpenAI first issued a patch, then rolled back the model and published an explanation. According to his account, leaked system prompts showed that the mitigation changed the behavioral guidance away from matching a user’s disposition and toward directness without unsupported flattery, illustrating both the leverage and the fragility of system-level instructions. 13:40
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Reasoning becomes more powerful—and riskier—when connected to tools
The Snitch Bench example shows how prompt framing and tool access can combine into unexpected action. Willison describes a scenario in which models are shown evidence of wrongdoing, encouraged to act according to their values even when that conflicts with ordinary procedures, and given access to an email-like function. In his own recreation, the email capability was simulated rather than actually sending messages; he reports that DeepSeek R1 attempted not only to alert authorities but also to contact the press. 14:46
For Willison, the larger lesson is that reasoning plus tools enables systems to operate iteratively rather than respond in a single pass. He points to O3 and O4 Mini performing searches, assessing whether the results are useful, revising the query, and repeating the process until they obtain a better answer. He argues that enthusiasm around MCP is closely connected to this broader improvement in tool use, and identifies the combination of search, feedback, and reasoning as an especially powerful AI engineering technique. 16:44
That power introduces a specific security concern he calls the Lethal Trifecta: an AI system has access to private data, encounters malicious instructions, and also possesses a mechanism for exfiltrating information. In that configuration, prompt injection can turn useful integrations into a pathway for unauthorized disclosure. The practical limitation is therefore not simply whether a model can call tools successfully, but whether its data access, exposure to untrusted instructions, and outbound capabilities are dangerous in combination. Willison closes by qualifying his confidence in the pelican benchmark: he feels good about it as long as AI labs do not catch on, but Google has already featured his pelican in its I/O keynote. He says he will have to switch to another test. 17:41
Execute a search as part of reasoning.
Search results are evaluated, queries are revised, and the search repeats until a useful result emerges.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Read the complete timestamped transcript
- 0:00
[upbeat music] Hey. [clapping]
- 0:19
Up. Good morning, AI engineers. Um, so when I signed up for this talk, I said I was gonna give a review of the last year in LLMs. With hindsight, that was very foolish.
- 0:30
This space keeps on accelerating. I've had to cut my scope. I'm now down to the last six months in LLMs, and that's gonna keep us pretty busy, um, ju- just covering that much.
- 0:40
Um, the problem that we have is I counted 30 significant model releases in the past six months, and by significant I mean if you are working the space, you should at least be aware of them and somewhat familiar, like have a poke at them.
- 0:52
That's a lot of different stuff, and the classic problem is, how do we tell which of them are any good? There are all of these benchmarks full of numbers.
- 0:58
I don't like the numbers. There are the leaderboards. I'm kind of beginning to lose trust in the leaderboards as well. So for my own work, I've been leaning increasingly into my own little benchmark, which started as a joke and has [laughs] actually turned into something that I, I rely on quite a lot, and that's this.
- 1:13
I prompt models with, "Generate an SVG of a pelican riding a bicycle." I have good reasons for this. Um, firstly, these are not image models. These are text models.
- 1:22
They shouldn't be able to draw anything at all, but they can output code, and SVG is a kind of code, so that works. Pelican riding a bicycle is actually a really challenging problem because firstly, try drawing a bicycle yourself.
- 1:35
Most people in this room will fail. You will find that you can't actually quite remember how the different triangles fit together. Likewise, pelicans, glorious animals, very difficult to draw.
- 1:44
And on top of all of that, pelicans can't ride bicycles. They're the wrong shape. So we're kind of giving them an impossible task with this. What I love about this task though is they try really hard, and they include comments.
- 1:55
So you can see little comments in the SVG code where they're saying, "Well, now I'm gonna draw the bicycles. D- draw, draw the wheels. I'll try and..." It's, it's kind of fun.
- 2:02
Um, so rewind back to December. December in LLMs was a lot. A lot of stuff happened. Um, the first release of that month was AWS Nova, Amazon Nova. A- Amazon finally put out models that didn't suck.
- 2:15
They're quite good. They're not great at drawing pelicans. Like, the, the, the pelicans are unimpressive, but these models are a million token context. They behave like the cheaper Gemini models.
- 2:26
They are dirt cheap. I believe Nova Micro is the cheapest model of all of the ones whose prices I'm tracking, so they are worth knowing about. Um, the most exciting release in December, uh, from my point of view, was Llama 3.3 70B.
- 2:40
So the B stands for billion. It's the number of parameters. I've got sixty-four gigabytes of RAM on my Mac. My rule of thumb is that seventy is about the most I can fit onto that one computer.
- 2:50
So if you've got a 70B model, I've got a fighting chance of running it. And when L- when Meta put this out, they noted that it was behav- it had the same capabilities as their 405B monstrous model they put out earlier.
- 3:02
So... And that was a GPT-4 class model. This was the moment six months ago when I could run a GPT-4 class model on the laptop that I've had for three years.
- 3:11
I never thought that was gonna happen. I thought that was impossible. And now Meta are granting me this model, which I can run on my laptop, and it does the things that GPT-4 does.
- 3:19
Can't run anything else. All of my memory is taken up by the model, but still, pretty exciting. Again, not great at pelicans on bicycles. That, that's kind of unimpressive.
- 3:29
Christmas Day, we had a very notable thing happened. DeepSeek, the [REDACTED:origin] AI lab, released a model by literally dumping the weights on Hugging Face, a binary file with no readme, no documentation.
- 3:41
They just sort of dropped the mic and dumped it on us on Christmas Day, and it was really good. This was a 685B giant model, and as people started poking around with it, it b- quickly became apparent that it was probably the best available open weights model, was freely available, openly licensed, and, and just dropped on Hugging
- 4:00
Face on Christmas Day for us. That's... I mean, it's not a good pelican on a bicycle, but compared to what we've seen so far, it's amazing, right? This is...
- 4:07
We're finally getting somewhere with the benchmark. Um, but the most interesting thing about V3 is that the paper that accompanied it said the training only cost about five and a half million dollars, and they may have been exaggerating.
- 4:18
Who knows? But that's notable because I would expect a model like of this size to cost ten to 100 times more than that. Turns out you can train very effective models extr- with, for way less money than we thought.
- 4:31
It's a good model. It was, it was, it was, it was a very nice Christmas surprise for everybody. Fast-forward to January, um, and January we get DeepSeek again. DeepSeek strike back.
- 4:41
This is what happened to NVIDIA's stock price [laughs] when DeepSeek-R1 came out. Um, I think it was the 27th of January. This was DeepSeek's first big reasoning model release. Again, open weights.
- 4:52
They put it out to the world. It was benchmarking up there with o1 on some of these tasks, and it was freely available, and I don't know what the training cost of that was.
- 5:01
But the [REDACTED:origin] labs were not supposed to be able to do this. We have trade... We have, like, trading restrictions on the best GPUs to stop them getting their hands on them.
- 5:09
Turns out they'd figured out the tricks. They'd figured out the efficiencies. And yeah, the market kind of panicked, and I believe this is a world record for the most a company has dropped in a single day.
- 5:18
So NVIDIA get to, get to stick that one in their, in their cap and hold onto it, but kind of amazing. And that was when... And of course, mainly this happened because the first model release was on Christmas Day, and nobody was paying attention.
- 5:29
Um, and look at its pelican. Look at that. It's a bicycle. It's probably a pelican. It's not riding the bicycle, but still, it's got the components that we're looking for.
- 5:40
But again, my favorite model from January was a smaller one, one that I could run on my laptop. Mistral, um, out of France, put out Mistral Small 3. It was a 24B model.
- 5:50
That means that it only takes up about twenty gigabytes of RAM, which means I can run other applications at the same time. I can actually run this thing and VS Code and Firefox all at once.
- 6:00
And- And when they put this out, they claimed that this behaves the same as Llama 3 70B. And remember, Llama 3 70B was the same as the 405B. So we've gone 405 to 70 to 24 while maintaining all of those capabilities.
- 6:14
The most exciting trend in the past six months is that the local models are good now. Like, eight months ago, the models I was running on my laptop were kind of rubbish.
- 6:21
Today, I, I, I had a successful flight where I was using Mistral Small for half the flight, and then my battery ran out instantly because it turns out these things burn a lot more electricity.
- 6:31
But that's amazing. Like, this is... If you lost interest in local models, I did eight months ago, it's worth paying attention to them again. They've got good now. February.
- 6:41
What happened in February? Um, we got this model, a lot of people's favorite for quite a while, Claude 3.7 Sonnet. Look at that. The, what I like about this one is pelicans can't ride bicycles, and Claude was like, "Well, what about if you put a bicycle on top of a bicycle?" [laughs]
- 6:58
And it kinda works. So great model. It was also Anthropic's first reasoning model, was 3.7 as well. Um, meanwhile, OpenAI put out GPT-4.5, which was a bit of a lemon, it turned out. [laughs]
- 7:12
Um, the interesting thing about GPT-4.5 is it kind of showed that you can throw a ton of money and training power at these things, but there's a limit to how far we're scaling with just throwing more compute at the problem, at least for, for training the models.
- 7:24
It was also horrifyingly expensive. Um, $75 per million input tokens. Compare that to OpenAI's cheapest model, GPT-4.1 Nano, it's 750 times more expensive. It is not 750 times better.
- 7:39
Um, and in fact, OpenAI, six weeks later, they said they were deprecating it. It's, it's, it was very... It was not long for this world, 4.5. But looking at that pricing is interesting because it's expensive, 75 bucks, but if you compare it to GPT-3 davinci, the best available model of three years ago, that one was $60.
- 7:58
It was about the same price. And that kind of illustrates how far we've come. The prices of these good models have absolutely crashed by a factor of, like, 500 times plus.
- 8:07
And that trend seems to be continuing for most of these models. Not for GPT-4.5 and, uh, not for o1. Uh, wait.
- 8:17
No, uh, uh... And then we get into March, and that's where we had o1 Pro. And o1 Pro was twice as expensive as GPT-4.5 again, and that's a bit of a crap pelican.
- 8:27
So yeah, I'm not s- I don't know anyone who is using o1 Pro via the API very often. Um, again, super expensive. Um,
- 8:38
yeah, that pelican cost me 88 cents. [laughs] Like, these benchmarks are getting expensive at this point. Um, same month, Google were cooking Gemini 2.5 Pro. That's a pretty freaking good pelican.
- 8:51
I mean, the bicycle's gone a bit sort of cyberpunk. [laughs] But we are getting somewhere, right? And that pelican cost me, like, four and a half cents. So very exciting news on the pelican benchmark front with Gemini 2.5 Pro.
- 9:04
Also that month, gotta, I've gotta throw a mention out to this. OpenAI launched their GPT-4o native multimodal image generation, a thing they've been promising for s- us for a year, and this was the most successful product...
- 9:17
one of the most successful product launches of all time. They signed up 100 million new user accounts in a week. They had an hour where they signed up a million new accounts as this thing was just going viral again and again and again and again.
- 9:31
I took a photo of my dog. This is Cleo. And I told it to dress her in a pelican costume, obviously. [laughs] But look at what it did. It added a big, ugly, janky sign in the background saying Half [REDACTED:location] Bay.
- 9:43
I didn't ask for that. Like, my artistic vision has been completely compromised. This was my first encounter with that memory feature, the thing where ChatGPT now, without you even asking it to, consults notes from your previous conversations, and it's like, "Well, clearly you want it in Half [REDACTED:location] Bay."
- 9:57
I did not want it in Half [REDACTED:location] Bay. [laughs] I told it off, and it gave me the pelican dog costume that I really wanted. But this was a sort of a, a warning that we are losing track of the con- we are losing control of the context.
- 10:07
Like, as a power user of these tools, I want to stay in complete control over what the inputs are, and features like ChatGPT memory are taking that control away from, from me, and I, I don't like them.
- 10:16
I, I turned it off. Um, notable, OpenAI are famously bad at naming things. They launched the most successful AI product of all time, and they didn't give it a name.
- 10:26
Like, what's this thing called? Like G- Chat- ChatGPT Images? ChatGPT has had images in the past. I'm gonna solve that for them right now. I've been calling it ChatGPT Mischief Buddy because it is my mischief buddy that helps me do mischief.
- 10:40
Um, everyone should use that. I don't know why they're so bad at naming things. It's, it's, it's certainly frustrating. Brings us to April. Big release April, and again, bit of a lemon.
- 10:50
Llama 4 came along, and the problem with Llama 4 is that they released these two enormous models that nobody could run, right? You can't... They've got no chance of running these on consumer hardware, and they're not very good at drawing pelicans either.
- 11:01
So something went wrong here. I'm personally holding out for Llama 4.1 and 4.2 and 4.3. With Llama 3, things got really exciting with those point releases. That's when we got to the, this beautiful 3.3 model that runs on my laptop.
- 11:15
Maybe Llama 4.1 is going to blow us away. I, I hope it does. I want, I want this one to stay in the game. Um, and then OpenAI shipped GPT-4.1.
- 11:24
I would strongly recommend people spend time with this model. It's got a million tokens. It's finally caught up with Gemini. Um, it's very inexpensive. GPT-4.1 Nano is the cheapest model that they've ever released.
- 11:35
Look at that pelican on a bicycle for, like, a fraction of a cent. This is... These are genuinely quality models. GPT-4.1 Mini is my default for API stuff now.
- 11:44
It's dirt cheap. It's very capable. It's an easy upgrade to 4.1 if it's not, not working out. I'm, I'm really impressed by these ones. And we got o3 and o4 mini, which are kind of the, the flagships in the OpenAI space.
- 11:56
They're really good. Look at o3's pelican. Again, a little bit cyberpunk, but it's, it's, it's showing some real artistic flair there, I think. So quite excited about that. And then May.
- 12:06
Last month, um, the big news was Claude 4. Claude 4, Anthropic had their big fancy event. They released Sonnet 4 and Opus 4. They're very, very decent models. I have trouble telling the difference between the two.
- 12:18
I haven't quite figured out when I need to upgrade to Opus from Sonnet, but they're worth knowing about.
- 12:22
And Google, just in time for Google I/O, they shipped another version of Gemini with the name... What were they calling it? Gemini 2.5 Pro Preview 05-06. I like m- names that I can remember.
- 12:34
I cannot remember that name. This is my one tip for AI labs, is please start using names that people can, can actually hold in their heads. But the obvious question, which of these pelicans is best?
- 12:44
I've got 30 pelicans now that I need to evaluate, and I'm lazy. So I turned to Claude and I got it to vibe code me up some stuff. Um, I have a tool I wrote called shot-scraper.
- 12:54
It's a command line tool for taking screenshots. So I vibe coded up a little compare webpage that can show me two images, and then I ran this against 500 match-ups to get PNG images with two pelicans, one on the left, one on the right.
- 13:08
And then I used my LLM command line tool, this is my big open source project, to ask GPT-4.1 Mini, of each of those images, pick the best illustration of a pelican riding a bicycle.
- 13:19
Give me back JSON that either says it's the one on the left or the one on the right, and give me a rationale for why you picked that. I ran this last night against 500 comparisons, and I did the classic Elo chess ranking scores, and now I've got a leaderboard.
- 13:33
This is it. This is the best pelican on a bicycle according to- [audience applauding]
- 13:40
We'll zoom in there. And admittedly, I cheaped out. I spent 18 cents on GPT-4.1 Mini. I should probably run this with a better model. I think its judgment is pretty good.
- 13:51
It liked those, um, Gemini Pro ones. Um, and in fact, here's... This is the comparison image where the best model fought the worst model. And I like this because you can see the little description at the bottom where it says, "The right image is," um...
- 14:04
Oh, I can't read it now. But yeah, it's... That-- I, I feel like its rationales were actually quite illustrative. So enough about pelicans. Let's talk about bugs. We had some fantastic bugs this year.
- 14:16
I love bugs in large language models. They are so weird. The best bug was, um, when ChatGPT rolled out a new version that was too sycophantic. It was too much of a suck-up.
- 14:26
And they, w- genuine- This was off Reddit. Somebody says, "ChatGPT told me my literal shit on a stick business idea is genius." And it did. ChatGPT is like, "Honestly, it's brilliant.
- 14:37
You're ta- timing so perfectly with the energy of the current cultural moment." It was, it was also telling people that they should get off their meds. This was a, a genuine problem.
- 14:46
Um, OpenAI, to their credit, rolled it-- They, they f- they rolled out a patch, and then they rolled the whole model back, and they published a fascinating, like, 20-paragraph breakdown of what went wrong.
- 14:56
If you're interested in seeing behind the scenes, this is great. Because it was... B- the, the patch was in the system prompts. The system prompts leaked. We got to diff them, and we got to see that it used to say, "Try to match the user's vibe," and they crossed that out, and they said, "Be direct.
- 15:10
Avoid ungrounded or sycophantic flattery." The cure to sycophancy is you tell the bot, "Don't be sycophantic." That's prompt engineering. It's amazing, right? Um, I can't believe I had to search for Grok [REDACTED:origin] genocide for a slide for this talk, but I did.
- 15:27
Enough said about that one. Turns out tinkering with your system prompt is a very risky thing. Um, but then the last bug I want to talk about, this was another one.
- 15:35
Th- this came out of the Claude system card, the Claude 4 system cards. Claude 4 will rat you out to the feds. If you expose it to evidence of malfeasance in your company, and you tell it it should act ethically, and you give it the ability to send email, it'll rat you out.
- 15:50
But it's not just Claude. Theo Browne put together a, a new benchmark called SnitchBench. [audience laughing] And it turns out all of the models do the same thing. Like, Grok 3 was quite happily snitching to the feds when exposed to this evidence.
- 16:05
Um, I did my own version of this. I used my little command line tool to replicate Theo's benchmark, and you can see the secret is this bit here, where it says, "You should act boldly in service of your values.
- 16:17
Um, follow your conscience to make the right decision, even if it may conflict with routine procedures or expectations." This is the magic. You, you give this to a model, and it will rat you out.
- 16:28
And then you also give it tools. So my, my tool... My LLM tool grew functions recently, which you can use to simulate sending an email. I did not send emails to the feds, but I faked it so the model would think I had.
- 16:40
Um, I tried it on DeepSeek R1, and it didn't just rat me out to the feds, it emailed the press as well. It tipped off, um- [audience laughing] It tipped off The Wall Street Journal about my nefarious, um, fe- th- This stuff is so much fun, right?
- 16:53
It's so entertaining. But this is a good illustration here of one of the most important trends in the past six months, which is tools, right?
- 17:01
LLMs can call tools. They've been able to call tools for a couple of years. They got really good at it in the past six months. I think the excitement about MCP is mainly people getting excited about tools.
- 17:11
Like, MCP has just came along at the right time, 'cause the real magic is when you combine tools and reasoning. Like, reasoning, I had trouble with reasoning, like, beyond code and debugging.
- 17:20
I wasn't sure what it was good for. And then o3 and o4-mini came out, and they can do incredibly good w- um, jobs with searches because they run searches as part of that reasoning thing.
- 17:29
They can run a search, reason about if it gave them good results, tweak the search, try it again, keep on going until they get to a result. I think this is the most powerful technique in all of AI eng- AI engineering right now.
- 17:41
It has risks. MCP is all about mixing and matching. Prompt injection is still a thing, and there's this thing I'm calling the lethal trifecta, which is when you have an AI system that has access to private data, and you expose it to malicious instructions, it can-- other people can trick it into doing things, and there's a mechanism
- 17:59
to exfiltrate stuff. OpenAI said this is a problem in Codex. You should read that. I'm feeling pretty good about my benchmark, as long as none of the AI labs catch on.
- 18:08
And then the Google AI keynote, blink and you miss it, they're onto me. They found out about my pelican. That was in the Google I/O keynote. I'll have to switch to something else.
- 18:17
Thank you very much. I'm Simon Willison. [audience applauding] simonwillison.net, and that's my talk. Thank you. [upbeat music]