Sprite checkpointing behavior?

Hey there, I have some questions around sprites checkpointing behavior. The docs seem to indicate that this checkpointing should automatically happen with the filesystem:

When Sprites become inactive, we remove their compute (and stop charging you!). When we assign new compute to Sprites, they come up with the exact same data on the filesystem.

The problem that I’m seeing is in numerous cases, my sprites move to ‘cold’ status, and then when they come back up, I no longer see the data. Do I need to explicitly invoke the checkpoint to log data to the filesystem or will this happen automatically? If it does happen automatically, are there any caveats or known issues for it?

I’ve seen this even for basic stuff like “claude code no longer thinks I am logged in”

Hmm, I think this might be my fault! After playing around with the CLI more I’m realizing some background jobs were deleting them, so consider this a request for an audit log UI instead :slight_smile:

To see the automatic checkpoints you’ll want to add the --include-auto flag to the command:

sprite checkpoint list --include-auto -s <Sprite-Name>

This should then include the checkpoints that were taken automatically (with names like auto-1776191193888 (auto))

Glad you got to the bottom of it! Cheers!