[FEATURE] Session-Based Permission Approval

Resolved 💬 5 comments Opened Jan 9, 2026 by rodroth Closed Apr 30, 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

---
Session-Based Permission Approval

Current situation:
Permission prompts offer two options:

  • Approve once (must approve each individual use)
  • Approve forever (added to settings.json permanently)

Problem:
There's no middle ground for users who want to run autonomous workflows within a single session without granting permanent tool access across all projects and all future sessions.

Proposed Solution

Add a third option in permission prompts:

  • "Allow for this session" - Approved tools reset when the session ends

This reduces permission fatigue while maintaining security boundaries.

Alternative Solutions

The only way is to fragment complex workflows into very small areas/sandboxes, and then give full permissions to a few of them, but coordination and overview suffers a bit, and pathing can be an issue.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Use case:
"Today I'm working on projects X and Y. I want Claude to run autonomously, handling whatever tools it needs (except DENY-listed commands), without constant approval prompts. But I don't want Claude to have carte blanche forever and for every project."

Additional Context

_No response_

View original on GitHub ↗

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