[DOCS] VS Code docs missing permission destination persistence (project/user/session)

Resolved 💬 2 comments Opened Feb 17, 2026 by coygeek Closed Mar 17, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

"Extension settings" table and permissions behavior

Current Documentation

The VS Code page documents the initialPermissionMode setting:

| initialPermissionMode | default | Controls approval prompts: default (ask each time), plan, acceptEdits, or bypassPermissions |

The permissions page (https://code.claude.com/docs/en/permissions) documents the general permission system but does not mention VS Code-specific permission destination behavior.

Neither page documents the ability to choose where a permission rule is saved (project, user, or session scope) or that this choice persists across sessions.

What's Wrong or Missing?

Claude Code v2.1.45 improved the VS Code extension's permission destination choice to persist across sessions. When a user grants a permission (e.g., "Yes, don't ask again"), the VS Code extension allows choosing where that permission is saved:

  • Project — saved to the project's settings
  • User — saved to user-level settings
  • Session — applies only to the current session

This destination choice now persists across sessions, so the extension remembers the user's preferred scope. This behavior is entirely undocumented — users have no way to discover from the docs that they can control where permissions are saved in VS Code, or that this preference persists.

Suggested Improvement

Add documentation to the VS Code page covering permission destination behavior. Suggested additions:

  1. In the "Extension settings" table or a new "Permission management" subsection, explain:
  • When granting a permission in VS Code, users can choose the destination scope (project/user/session)
  • This destination preference persists across sessions
  • How each scope differs (project = .claude/settings.json, user = ~/.claude/settings.json, session = temporary)
  1. Cross-reference the existing permissions documentation for the rule format and precedence.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/vs-code | Extension settings table — no mention of permission destination |
| https://code.claude.com/docs/en/permissions | General permission system — no VS Code-specific destination behavior |

Total scope: 2 pages affected

Source: Changelog v2.1.45 — "[VSCode] Improved permission destination choice (project/user/session) to persist across sessions"

View original on GitHub ↗

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