[FEATURE] Persistent, adjustable approval preferences for bash command prompts during multi-agent sessions

Resolved 💬 2 comments Opened Apr 9, 2026 by mwigge Closed May 23, 2026

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

The current bash command approval flow offers:

  • 1) Yes
  • 2) No
  • Occasionally Yes, don't ask again
  • Ctrl-C to abort

This works well for single-agent sessions, but becomes disruptive when running multiple agents in parallel. Interrupting one agent's prompt can block or cancel the entire session, and the binary yes/no model doesn't allow nuanced feedback mid-run.

Proposed Solution

Add a third persistent option to every bash command prompt:
1) Yes
2) No
3) Adjust preference and continue
Option 3 would:

  • Open a short inline prompt where the user can describe a rule (e.g. "always approve git status but ask for git commit")
  • Apply that rule immediately for the remainder of the session
  • Optionally persist it to settings.json auto-approve rules

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

You launch 3 agents in parallel: one running tests, one refactoring a module, one updating a schema. Mid-run, the refactoring agent hits a git commit prompt and waits. You want to approve it — but you also want to tell it "don't ask me about git commit again this session, I trust it". Your only options today are:

  • Say yes (asked again next commit)
  • Say "yes, don't ask again" (too broad — now nothing asks)
  • Hit Ctrl-C (kills the agent, loses all progress)

With option 3, you'd type: "approve git commit for the rest of this session" — the agent continues, the rule applies, and the other two agents are unaffected.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗