Remove -y flag from browsers delete, make non-interactive#85
Merged
Conversation
The -y/--yes confirmation flag on `kernel browsers delete` was overly cautious and not necessary. It also frequently trips up LLMs that attempt to use the CLI, as they either forget to pass the flag or get stuck waiting for interactive confirmation that never comes. Browser deletion is already an idempotent operation (deleting a non-existent browser succeeds), so requiring confirmation adds friction without meaningful protection.
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.
Summary
-y/--yesconfirmation flag fromkernel browsers deleteThe confirmation prompt was overly cautious and not necessary:
LLM compatibility: The
-yflag frequently trips up LLMs that use the CLI - they either forget to pass it or get stuck waiting for interactive confirmation that never comes in their execution environment.Idempotent operation: Browser deletion is already idempotent (deleting a non-existent browser succeeds), so requiring confirmation adds friction without meaningful protection.
Consistency: Other delete commands in the CLI (like browser session cleanup) don't require confirmation.
Test plan
go build ./...succeedskernel browsers delete <id>now deletes without promptingNote
Makes
kernel browsers deletenon-interactive and removes confirmation flags.-y/--yesflag and all interactive confirmation logic fromBrowsersCmd.Delete; command is now idempotent and non-interactiveDeletenow triesDeleteByIDthen persistent delete, treating not-found as success; prints a single success message--yesin CLI (runBrowsersDelete) and README examplesWritten by Cursor Bugbot for commit 5b74b84. This will update automatically on new commits. Configure here.