feat(cli): Graceful CLI interrupt handling on Ctrl+C#114
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
521870d to
8c6923f
Compare
8c6923f to
998a095
Compare
998a095 to
7d5202b
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
Route interrupt message through Ink rendering pipeline (TTY) and logPlain (non-TTY) instead of raw stderr writes that corrupt Ink's cursor tracking. The abort signal triggers the message in both paths. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
7d5202b to
b95cd5f
Compare
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.
When the user presses Ctrl+C during a scan, the process now collects partial
results from completed skills and renders them instead of hard-exiting with
no output.
Behavior:
render partial results with "Interrupted" banner, exit 130
The abort controller was already wired through the SDK and checked at the
hunk level, so running tasks finish quickly after signal. The main change is
removing the immediate
process.exit(130)and letting the normal outputpath run with an interrupted flag.
Closes #109