Allow exporting session-granted permissions to persistent settings

Resolved 💬 2 comments Opened Feb 21, 2026 by phelps-sg Closed Feb 23, 2026

Feature Request

When using Claude Code interactively, I frequently grant permissions during a session (e.g. file edits, bash commands). When I exit and start a new session, all those permissions are lost and I have to re-approve them one by one.

Current behaviour: Permissions granted during a session are ephemeral (except Bash commands approved with "don't ask again"). There's no way to review what was granted during the session or persist those approvals to settings files.

Desired behaviour: A command (e.g. /permissions export or /permissions save) that snapshots all permissions granted during the current session and writes them to the appropriate settings file (~/.claude/settings.json or .claude/settings.local.json), optionally with a confirmation/review step so the user can cherry-pick which ones to persist.

Why this is useful: Over the course of a session, the set of permissions I grant naturally reflects my actual workflow. Being able to capture that as a baseline for future sessions would save repeated approval friction without requiring me to manually construct permission rules up front.

Alternatives considered

  • Manually adding rules to settings files — works but requires knowing the exact syntax and remembering what was approved
  • Using bypassPermissions mode — too broad, loses the safety benefits of the permission system
  • Using acceptEdits mode — only covers file edits, not Bash commands

View original on GitHub ↗

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