[FEATURE] Add session-scoped command permissions

Resolved 💬 3 comments Opened Feb 2, 2026 by mimkorn Closed Feb 2, 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

Do you want to proceed?
❯ 1. Yes

  1. Yes, and don't ask again for curl commands in /project-path
  2. Type here to tell Claude what to do differently

Very often what I want to do is to allow something to happen in this session without asking, but not to add it to the project permanently. For example, I wouldn't want to allow websearch in general permanently for a project, but sometimes when I know I will be doing a heavy search conversation, I don't want to be confirming each and every one. However, if I would allow it to not ask again, then I have to remember to correct the settings file afterwards.

Proposed Solution

Do you want to proceed?
❯ 1. Yes

  1. Yes, and don't ask again for curl commands in this session
  2. Yes, and don't ask again for curl commands in /project-path
  3. Type here to tell Claude what to do differently

Alternative Solutions

Alternatively cycleable option for just this session. Cycleability was proposed in https://github.com/anthropics/claude-code/issues/11073 However to my surprise it did not include the option for just the session.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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