[FEATURE] Add "Allow for this session" option to permission prompts

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

When Claude Code prompts for permission, the options are:

Yes (one-time)
Yes, always allow for this project (permanent)
No

There's no middle ground. Either I click "Yes" repeatedly for the same action, or I permanently add permissions I only need temporarily.

Proposed Solution

Add a session-scoped option:
Do you want to proceed?
❯ 1. Yes

1. Yes, allow for this session
2. Yes, always allow for this project
3. No

Use Cases

• Exploring an unfamiliar codebase without permanently expanding permissions
• One-off tasks (migrations, debugging) that need temporary broader access
• Avoiding stale permissions accumulating in config files

Alternative Solutions

--allowedTools at launch (requires knowing permissions upfront)
Manually cleaning config after sessions
Repeatedly clicking "Yes"

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

• Debugging something that touches node_modules/ — I need to read in there temporarily but don't want that permanently in my config
• Trying out different build commands while setting up CI — lots of make and docker calls I won't need once it's working
• Cloned a repo to evaluate it, want Claude to read freely while I explore, but I'll delete it tomorrow anyway
• Testing against a staging API endpoint — need WebFetch for that URL right now, definitely don't want it allowlisted forever

Additional Context

_No response_