claude-code - 💡(How to fix) Fix Approve-once-per-session for repeated identical tool calls

Preflight Checklist

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

Problem Statement

When a pipeline fans out to multiple parallel sub-agents (e.g., 10–15 simultaneous Jira lookups), each agent independently triggers a permission prompt for the same tool. The user is required to approve each prompt individually, which is impractical and inefficient at scale.

Proposed Solution

Implement a session-scoped approval mechanism. Once a user approves a tool call (same tool name + same permission scope) during a session, all subsequent calls to that tool within the same session should be auto-approved. This avoids the need for repeated prompts and does not require permanent allowlisting.

A confirmation banner, such as "Approved jira_search for this session (3 more auto-approved)," should be displayed to provide transparency and session-level visibility without interrupting workflow.

Alternative Solutions

The only current workaround is to permanently allowlist the tool via the project .claude/settings.json. While effective, this requires upfront configuration and is broader than a session-scoped approval.

Priority

Critical - Blocking my work

Feature Category

MCP server integration

Use Case Example

This feature is especially needed for multi-agent pipelines (fan-out orchestrators) that launch N parallel sub-agents, all calling the same MCP tool. The current model generates N blocking prompts, which undermines the benefits of parallel execution.

Additional Context

No response