Opus 5 lets Claude Code remove instructions it no longer needs

Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

1. 3:19

   injection, the other side of the coin is now the system prompt. Let's talk a bit about the new release. You actually deleted over 80% of the system prompt from CLAW code. Tell us more. about that? I think something that a lot of people might not realize is cloud code as a product and as a harness is just always changing. We're always adding stuff. We're always deleting stuff. Every time that a new model comes out, we delete a bunch of the system prompt, change a bunch of the system prompt. We change the set of tools all the time. We change the prompts for the tools all the time. And the reason is every model is very different. So something that you did for one model maybe three months ago, it just might not translate at all to the next model. And so one thing about Opus 5 is it's just really intelligent. And a lot of the stuff in the

2. 4:16

   system prompt was correcting for these behaviors that the model should have known, but it didn't. Now Opus 5 just does it. So yeah, we deleted 80% of the system prompt. You can actually try deleting the rest of it too. So when you run cloud code, you can just do like dash dash system prompt and set whatever system prompt you want, if you want to experiment with it. And another thing that you can try is simple mode. So this is actually this kind of undocumented feature. If you do cloud code simple equals one, like this environment variable, and then you run cloud, it'll delete all the system prompts, including from the tools. And we actually use this as a sort of ablation to figure out, is the prompt useful? And what's interesting is that the model is actually a little bit more intelligent without these prompts. That's something that we've been

3. 5:07

   finding. But when you use quad code as a product, you do actually want some of these prompts because it helps you use the product and it helps the product behave and the model behave in the way that you would want when you're using it as a person. I think the thing that's really fascinating in this era of building, basically you have built the best hardness in the world for Cloud, and that's Cloud Code.

4. 5:30

   From what I'm hearing, for every model released, you basically delete all of the code base, delete all of the prompt, and start from scratch every time. That in the old world would have been not something started would have done for the product. It's like press delete every six months for everything. That's right. To be fair, we don't delete the entire code base, but we do delete a lot. So every time there's a new model, we try, in research, we call this ablation. And so what this means is you delete the entire system prompt, and then you bring it back line by line to figure out what is the impact of each individual line. It's sort of like an eval, and you can kind of evaluate it, and the ablation, essentially, it's an eval, but you delete things to figure out the impact. And yeah, we do the same thing for tools. We unship tools all the time. We delete code in

5. 6:18

   the harness all the time if you look at actually the code that's in the cloud code harness today almost all of it is about safety and permissions and static analysis and there's a bunch of ui code