Earlier quoted context omitted.
With prefix caching, you get checkpoints for free. Do you mean that?
No. Prefix caching is just an optimisation on the server side. What Kimi CLI does is insert tags that include a checkpoint marker with an id. The model is then given a tool that allows the model to decide to roll back to a checkpoint + a message containing any additional useful information. It's specifically instructed to use that tool[1] in cases like when it has inadvertendly read a large file where most of the con…
Prefix caching automatically detects priorly read tokens -> more fained grained checkpoints then. With prefix caching you don't have to ask for a checkpoint, its automatic.
One way or the other, a prefix is saved. Only the additional info how to continue is new.