Add CLI flag to configure checkpoint file location#47
Merged
phrp720 merged 3 commits intophrp720:masterfrom Feb 11, 2026
Merged
Add CLI flag to configure checkpoint file location#47phrp720 merged 3 commits intophrp720:masterfrom
phrp720 merged 3 commits intophrp720:masterfrom
Conversation
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.
The sync agent currently always creates its checkpoint file (checkpoint.json) in the current working directory.
This makes it difficult to:
In a project I was working on, I needed to control where the checkpoint file is stored.
Solution
This PR introduces a configurable checkpoint file location that can be set via a CLI flag.
Changes
checkpointsetting to configuration (settings.Settings.CheckpointFile)Usage
Notes
checkpoint.jsonis created in the current working directory when the new CLI flag is not used.