Add checkpoint sync destination picker to entire enable#1172
Open
evisdren wants to merge 5 commits into
Open
Conversation
During `entire enable`, users are now prompted to choose where checkpoint data should sync: this repo's remote (default), a separate private checkpoint repo, or local-only. This makes the checkpoint destination an explicit choice rather than a hidden default, helping users avoid accidentally pushing sensitive transcript data to public repos. Interactive mode shows a huh Select picker with three options. Selecting "A separate private checkpoint repo" prompts for the repo in github:owner/repo format. Non-interactive mode (--yes/CI) prints an informational notice with the configure command. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: b3257fa78e5b
Adds a blank line between "Selected agents:" and the checkpoint sync footer text so they don't run together visually. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: 78193a12b231
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a checkpoint sync destination selection step to the interactive entire enable flow, aiming to guide users toward syncing checkpoints to the current repo remote, a separate private checkpoint repo, or keeping checkpoints local-only.
Changes:
- Introduces an interactive picker (and follow-up input for separate repo) to set checkpoint sync behavior during
entire enable. - Adds non-interactive/
--yesoutput that explains how to configure a private checkpoint repo. - Adds unit tests covering non-interactive output and option application/validation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| cmd/entire/cli/setup.go | Adds the checkpoint sync picker/notice and applies the choice into EnableOptions during runEnableInteractive. |
| cmd/entire/cli/setup_test.go | Adds unit tests for non-interactive notice output and applyCheckpointSyncChoice behavior/validation. |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: 0e5c17c5d9e7
…g opts - Skip checkpoint sync prompt/notice when --checkpoint-remote or --skip-push-sessions is already provided via CLI flags - Each branch in applyCheckpointSyncChoice now explicitly clears the conflicting field to prevent stale values from leaking through Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: 7a0415782479
Contributor
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
1 issue from previous review remains unresolved.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 5741a6c. Configure here.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: 1421fb74752d
blackgirlbytes
approved these changes
May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://entire.io/gh/entireio/cli/trails/346
Summary
CleanShot.2026-05-09.at.13.46.41-converted.mp4
entire enableasking where checkpoints should sync: this repo's remote, a separate private checkpoint repo, or local-only--yes/CI) prints an informational notice with theentire configure --checkpoint-remotecommandgithub:owner/repoformat and validates the input--skip-push-sessionsTest plan
this-remote,local,separate-repo)--yesmode outputmise run fmt && mise run lintcleanentire enableinteractively and verify picker renders correctlyentire enable --yesand verify notice prints🤖 Generated with Claude Code
Note
Medium Risk
Changes the
entire enableinteractive flow to set checkpoint-sync related strategy options, which could affect where session transcripts get pushed and introduce new prompt/CI behavior.Overview
Adds an interactive checkpoint-sync destination picker to
entire enable, letting users choose syncing to the current repo remote, a separate private checkpoint repo (validatedgithub:owner/repo), or local-only (sets--skip-push-sessions).In
--yes/non-interactive mode, it skips prompting and prints a notice with guidance forentire configure --checkpoint-remote, plus a sensitivity/redaction footer. Includes unit tests covering all branches, skip conditions, and invalid/unsupported repo inputs.Reviewed by Cursor Bugbot for commit 5741a6c. Configure here.