Returning back to the Anthropic compiler attempt: one of the steps that the agent failed was the one that was more strongly related to the idea of memorization of what is in the pretraining set: the assembler. With extensive documentation, I can’t see any way Claude Code (and, even more, GPT5.3-codex, which is in my experience, for complex stuff, more capable) could fail at producing a working assembler, since it is quite a mechanical process. This is, I think, in contradiction with the idea that LLMs are memorizing the whole training set and uncompress what they have seen. LLMs can memorize certain over-represented documents and code, but while they can extract such verbatim parts of the code if prompted to do so, they don’t have a copy of everything they saw during the training set, nor they spontaneously emit copies of already seen code, in their normal operation. We mostly ask LLMs to create work that requires assembling different knowledge they possess, and the result is normally something that uses known techniques and patterns, but that is new code, not constituting a copy of some pre-existing code.
When we run timeTravel(checkoutFlow, traceLog), it will actually exercise our checkout workflow, and produce the following output. With that, we’ve successfully executed a production execution trace locally, all without touching any database or external service:
。业内人士推荐爱思助手下载最新版本作为进阶阅读
中國防疫人員入民宅「無害化處置」寵物狗，引發眾怒2021年11月16日
Дания захотела отказать в убежище украинцам призывного возраста09:44
FT Weekend Print delivery