[FEATURE] Add "No, but continue" option to command execution prompts

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When Claude Code suggests executing a command, I'm presented with three options: "Yes", "Yes, and ask again", or "No". However, there's a missing workflow option that disrupts my development process.

The Problem:
When I select "No" to reject a potentially risky command (like rm -rf or sudo operations), Claude Code stops its entire workflow and waits for my next instruction. This forces me to manually tell Claude to continue with the remaining tasks, breaking the flow and requiring additional back-and-forth communication.

Why I Need This:
During coding sessions, Claude often suggests 5-10 sequential commands. Sometimes one command in the middle is risky or unnecessary, but I want Claude to skip that specific command and continue with the rest of the plan automatically. Currently, I have to reject the command and then manually type "please continue with the next steps" every single time.

Proposed Solution

Add a fourth option to the command execution prompt: "No, but continue"

Ideal User Experience:

1. Claude suggests a command
2. I see four options:

• Yes
• Yes, and ask again
• No
• No, but continue ← NEW

1. When I select "No, but continue":

• The current command is skipped (not executed)
• Claude automatically proceeds to the next step in its plan
• No additional manual input required from me

UI Mockup:

Execute command: rm -rf temp_files/

[Yes] [Yes, and ask again] [No] [No, but continue]

When "No, but continue" is selected:

⊘ Command skipped by user
↻ Continuing with next step...

Alternative Solutions

Current Workaround:

1. Select "No"
2. Manually type in chat: "Skip this command and continue"
3. Wait for Claude to acknowledge and proceed

This works but is tedious and breaks the development flow.

Alternatives Considered:

• Auto-approve lists: Using settings like autoRejectCommands - but this doesn't allow per-situation decisions
• "Yes, and ask again": Too permissive - executes the risky command first
• Keyboard shortcuts: Would still require manual continuation instruction

None of these alternatives provide the streamlined "skip and auto-continue" workflow I need.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Scenario: Cleaning up a React project and restarting the dev server

Claude's plan involves 5 commands:

1. npm run build - build the project
2. rm -rf node_modules/.cache - clear cache
3. rm -rf dist/ - remove old build
4. sudo npm install -g some-tool - install global tool
5. npm run dev - restart dev server

Current Flow (Frustrating):

• Commands 1-3: I click "Yes" → ✅ Executed
• Command 4: Contains sudo - risky! I click "No" → ⊘ Rejected
• Claude stops and waits 😞
• I must type: "Skip that command and continue with npm run dev"
• Claude acknowledges and executes command 5

Desired Flow (With "No, but continue"):

• Commands 1-3: I click "Yes" → ✅ Executed
• Command 4: Contains sudo - risky! I click "No, but continue" → ⊘ Skipped
• Claude automatically proceeds to command 5 → ✅ Executed
• Total interaction: 4 clicks instead of 4 clicks + typing + waiting

Time saved per occurrence: ~15 seconds
Occurrences per day: ~15 times
Daily time saved: ~4 minutes of pure efficiency gain

Additional Context

Similar Features in Other Tools:

• GitHub Actions: "Skip this job but continue workflow"
• GitLab CI: "Allow failure" option for pipeline steps
• Make/Build tools: Continue on error with -k flag

Technical Implementation Suggestion:

enum CommandApprovalResult {
  APPROVED,
  APPROVED_ASK_AGAIN,
  REJECTED_AND_STOP,
  REJECTED_BUT_CONTINUE  // ← NEW
}

if (result === CommandApprovalResult.REJECTED_BUT_CONTINUE) {
  logCommandSkipped(command);
  return continueToNextStep();
}

User Setting (Optional Enhancement):

{
  "claude-code.defaultRejectionBehavior": "stop" | "continue"
}

This would let users who frequently want to continue set that as default behavior for "No".

Mockup Screenshot:
(Imagine a prompt dialog with four horizontal buttons, the new "No, but continue" button styled in a neutral color between "No" (red-ish) and "Yes" (green-ish))

---

Impact Summary:
This small UX improvement would dramatically reduce friction in the command approval workflow, especially for users who work with Claude Code on complex, multi-step tasks involving both safe and potentially risky commands.