[FEATURE] Temporary task-scoped permission approval (approve all for this prompt)

Resolved 💬 4 comments Opened Mar 24, 2026 by babyhuey Closed May 1, 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

When Claude is working through a multi-step task (e.g. rebasing 5 branches, resolving merge conflicts across many files), the permission prompts become a bottleneck. You end up hitting "y" dozens of times for bash commands and file edits that are all part of the same logical task.

The current options are:

  • Approve once — too granular when Claude needs 30+ tool calls for one task
  • Approve for session — too broad, you lose oversight for the rest of the conversation
  • --dangerously-skip-permissions — no oversight at all

There's no middle ground for "I trust what you're doing right now, go ahead and finish this task, but ask me again on the next prompt."

Proposed Solution

Add a temporary approval scope: "approve all for this response" (or "this prompt" / "this run"). When selected, all subsequent tool calls triggered by the current user prompt are auto-approved. Once Claude finishes responding and waits for the next user input, permissions revert to normal.

This could be an option at the permission prompt, e.g.:

  • y — approve once
  • r — approve all for this response/run
  • a — approve for this session
  • n — deny

Prior Art

This has been requested multiple times and keeps getting closed as duplicate/stale, which suggests it's a real pain point:

  • #26424 — Task-scoped permission approval for multi-step operations (closed/stale)
  • #33645 — Scoped auto-approve (closed/duplicate)
  • #34945 — Add "approve for this response" permission scope (closed/duplicate)

Alternative Solutions

A time-boxed approval (e.g. "approve for the next 5 minutes") could also work but is less intuitive than tying it to the current response.

View original on GitHub ↗

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