Skip to main content
Configure a checkpoint remote when checkpoint history should follow a different sharing boundary than your source code, such as keeping agent transcripts private for a public project. Your code continues to live in the main repository, and Entire pushes checkpoint data to the separate one.

​
Configure the Checkpoint Remote

Create a separate, empty repository for checkpoint data, then run this from your project:
The value uses the format provider:owner/repo. Currently, github is the supported provider. This writes:
.entire/settings.json
Commit and push .entire/settings.json when the checkpoint remote should apply to the whole project. That setting is what entire.io reads to locate checkpoint data.

​
Keep Checkpoints under the Same Owner

Use a checkpoint repository with the same owner or organization as your code repository. Code at github.com/acme/app pairs with github:acme/app-checkpoints, because acme owns both. Entire won’t push checkpoint data to a repository under a different owner. That is intentional: it protects forks, keeping fork contributors from needing write access to the upstream project’s checkpoint repository.

​
Push Behavior

When you push code, Entire pushes the configured checkpoint data to the checkpoint repository separately, using the same protocol as your Git remote. If the checkpoint repository cannot be reached, your main Git push still succeeds. Entire keeps the checkpoint data locally and warns that it could not sync.