Add --force flag to override stale locks#63
Merged
jonathonbyrdziak merged 1 commit intomasterfrom Mar 21, 2026
Merged
Conversation
When a previous protocol start was killed (Ctrl+C), the lock file persists and blocks subsequent runs. The --force flag releases any existing lock and re-acquires it. Propagates to subcommands (git:pull). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
--force/-fflag toprotocol startandgit:pull--forceto subcommands--force, the error message now tells users about the flagTest plan
protocol startmid-run, then runprotocol start— see lock error with hintprotocol start -f— overrides the stale lock and proceedsprotocol start -v -f— both flags work together🤖 Generated with Claude Code