Skip to main content
When checkpoint history should stay on the machine that captured it, turn off automatic checkpoint pushes. Entire keeps capturing checkpoint data and stops sending it to GitHub or another remote. Use this for local experiments, or for repositories where you do not need checkpoint history available from another device. The tradeoff is that teammates cannot open a local-only checkpoint, and neither can you from another machine.

​
Just Your Clone

Write the setting to local settings:
This writes push_sessions: false to .entire/settings.local.json:
.entire/settings.local.json
.entire/settings.local.json is gitignored and takes precedence over project settings, so nobody else in the repository is affected.

​
The Whole Repository

To disable checkpoint pushes for everyone working in the repository, use project settings instead:
This writes the same setting to .entire/settings.json. Commit that file when the behavior should apply to the whole project. See Local, Project, and Global Settings for how the layers resolve.

​
Turn Pushing Back On

--skip-push-sessions only sets the flag; there is no flag that clears it. Set push_sessions back to true in the settings file you wrote it to, or delete the key to fall back to the default:
.entire/settings.local.json
entire status then names the checkpoint sync destination and counts the checkpoints waiting to reach it.