Feature Request: Add 'Allow always (save to settings)' permission option

Problem

Currently, when Claude Code prompts for permission to execute a command, the available options are:

• Allow once
• Allow for session

There is no option to permanently save the permission to the user's settings file (~/.claude/settings.json).

This becomes frustrating as users must repeatedly grant the same permissions across sessions.

Current Workaround

Users must manually edit ~/.claude/settings.json to add permissions, which is tedious and requires knowledge of the file structure.

Proposed Solution

Add a third option when prompting for permissions:

• "Allow always (save to settings)"

This option would:

1. Allow the current action
2. Automatically append the permission pattern to ~/.claude/settings.json under permissions.allow

Additional Issue

Even with permissions already configured in the settings file, Claude Code sometimes prompts again at the start of a new session. The system should better respect already-saved permissions.

Benefits

• Better UX - users don't have to repeatedly grant the same permissions across sessions
• Reduces friction for power users
• Eliminates the need to manually edit config files
• Follows the principle of progressive permission granting

Example Flow

Claude wants to run: rm -rf node_modules

[Allow once] [Allow for session] [Allow always (save to settings)] [Deny]

Selecting "Allow always" would add "Bash(rm *)" to the user's settings file permanently.