add "--checkpoint-remote" to "configure"

[Soph]

Enabling a checkpoint-remote should be just passing the flag with a remote to "entire configure"

---

Note

Medium Risk
Modifies entire configure/entire enable control flow to sometimes skip interactive agent setup and write settings directly, which could change behavior in already-configured repos if flag detection is incorrect.

Overview
Adds --checkpoint-remote (and a shared strategy flags detection helper) to entire configure/entire enable, allowing strategy settings to be updated directly in an already-configured repo.

Introduces a settings-only path (updateStrategyOptions) that updates strategy_options without touching agent hooks, and updates entire enable to apply these flags before checking/printing the "already enabled" status.

^{Written by Cursor Bugbot for commit 83ad1be. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: updateStrategyOptions ignores --local flag, always writes project settings
  • Updated updateStrategyOptions to use determineSettingsTarget (matching runEnableInteractive) to choose between SaveEntireSettings and SaveEntireSettingsLocal based on the --local/--project flags, and display the correct config path.

Or push these changes by commenting:

@cursor push aedbdfc310

Preview (aedbdfc310)

diff --git a/cmd/entire/cli/setup.go b/cmd/entire/cli/setup.go
--- a/cmd/entire/cli/setup.go
+++ b/cmd/entire/cli/setup.go
@@ -81,11 +81,32 @@
 
 	opts.applyStrategyOptions(s)
 
-	if err := SaveEntireSettings(ctx, s); err != nil {
-		return fmt.Errorf("failed to save settings: %w", err)
+	entireDirAbs, err := paths.AbsPath(ctx, paths.EntireDir)
+	if err != nil {
+		entireDirAbs = paths.EntireDir
 	}
+	shouldUseLocal, showNotification := determineSettingsTarget(entireDirAbs, opts.UseLocalSettings, opts.UseProjectSettings)
 
-	fmt.Fprintf(w, "✓ Settings updated (%s)\n", configDisplayProject)
+	if showNotification {
+		fmt.Fprintln(w, "Info: Project settings exist. Saving to settings.local.json instead.")
+		fmt.Fprintln(w, "  Use --project to update the project settings file.")
+	}
+
+	if shouldUseLocal {
+		if err := SaveEntireSettingsLocal(ctx, s); err != nil {
+			return fmt.Errorf("failed to save settings: %w", err)
+		}
+	} else {
+		if err := SaveEntireSettings(ctx, s); err != nil {
+			return fmt.Errorf("failed to save settings: %w", err)
+		}
+	}
+
+	configDisplay := configDisplayProject
+	if shouldUseLocal {
+		configDisplay = configDisplayLocal
+	}
+	fmt.Fprintf(w, "✓ Settings updated (%s)\n", configDisplay)
 	return nil
 }

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

Comment @cursor review or bugbot run to trigger another review on this PR

[Copilot]

Pull request overview

This PR extends the entire configure flow to support configuring checkpoint strategy behavior via CLI flags, so enabling a checkpoint remote can be done by passing a flag rather than going through agent selection.

Changes:

• Adds --checkpoint-remote flag to entire configure.
• Introduces a “settings-only” path in configure to update strategy options without prompting for agents when already set up.
• Updates entire enable to apply any provided strategy flags before enabling (and suppresses the “already enabled” message when only strategy flags were applied).