claude-code - 💡(How to fix) Fix [FEATURE] Add "Allow for Session" permission option to Claude Code Desktop [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48479Fetched 2026-04-16 06:59:01
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Add Allow for Session as a permission option in Claude Code Desktop's tool approval dialog — something the VS Code Claude extension already supports.

Root Cause

Add Allow for Session as a permission option in Claude Code Desktop's tool approval dialog — something the VS Code Claude extension already supports.

RAW_BUFFERClick to expand / collapse

Summary

Add Allow for Session as a permission option in Claude Code Desktop's tool approval dialog — something the VS Code Claude extension already supports.

Current behavior (Desktop)

When a tool requires approval, Claude Code Desktop offers two buttons:

  • Allow Once — one-time approval
  • Always Allow — persists to the project's .claude/settings.local.json

There is no way to grant a permission for the current session only.

VS Code extension (for reference)

The VS Code Claude extension also shows two buttons, but the second button can be toggled between Allow for Session and Allow for Project. So from a single prompt the user can pick:

  • Allow Once
  • Allow for Session (default of the second button)
  • Allow for Project (the other toggle state)

This gives three effective tiers without adding a third button.

Requested behavior

Bring the same capability to Desktop — ideally via the same toggle pattern on the second button, so users can choose between session-scoped and project-scoped trust when approving a tool. The exact UI is up to the team; what matters is that Allow for Session becomes reachable from the approval dialog.

Use case: granular trust without polluting settings.local.json

Session-scope fills a real gap between one-time and project-wide trust:

  • I frequently want to approve a tool for the duration of the current work session without committing it to the project's persistent permission list. With only the binary choice on Desktop today, I either click "Allow Once" dozens of times per session or accumulate entries in settings.local.json that I'd rather not persist.
  • For exploratory work or debugging, session-scope lets me move quickly without making long-term commitments about what the project is allowed to do.
  • settings.local.json stays cleaner — fewer ad-hoc entries means less manual cleanup later.

In VS Code this is my most-used option, and I'd expect the same on Desktop once available.

Environment

Claude Code Desktop on Windows 11.

extent analysis

TL;DR

Implement a toggle button in the Claude Code Desktop tool approval dialog to allow users to choose between "Allow for Session" and "Allow for Project" permissions.

Guidance

  • Review the VS Code Claude extension's implementation of the Allow for Session and Allow for Project toggle to understand the desired behavior.
  • Update the Claude Code Desktop's approval dialog to include a similar toggle button, allowing users to switch between session-scoped and project-scoped trust.
  • Ensure the new toggle button is intuitive and easy to use, with clear labeling and minimal additional UI changes.
  • Test the updated approval dialog to verify that it functions as expected and provides the desired granular trust options.

Example

No code snippet is provided as the issue does not include specific implementation details.

Notes

The implementation may require updates to the underlying permission management system to support session-scoped permissions.

Recommendation

Apply a workaround by modifying the approval dialog to include the Allow for Session option, as this will provide the desired functionality and align with the existing VS Code extension behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING