Skip to main content

After every prompt completion, Clark automatically creates a checkpoint so you can track changes and restore to a previous generation at any point while building.
Clark creates checkpoint after generation
Restore to a previous checkpoint
When restoring a checkpoint, the app’s edit state is reset to the state it was in at the time of the checkpoint. All chat messages that occurred after this checkpoint are archived, effectively resetting Clark’s memory to this checkpoint.

​
Viewing change history

To see a log of all changes during your editing session, select the Versions section of the left navigation then switch to the History tab.
Track Clark changes under versions history

​
Committing and deploying

When you’re ready to create a named commit to be checked into source control, select the Commits tab, describe your changes, and commit to your current branch. This kicks off a build that creates a preview link of your committed changes. Once the build completes and you’ve reviewed the preview, select your commit and Deploy to Production to make your changes live for end users.
Commit uncommitted changes
Deploy committed changes
For more info on committing and deploying changes in Superblocks, see version control.