Description
The --dangerously-skip-permissions flag's help text states:
--dangerously-skip-permissions Bypass all permission checks. Recommended only for sandboxes
with no internet access.
However, the workspace trust prompt ("Quick safety check: Is this a project you created or one you trust?") is not bypassed by this flag. This is misleading — "bypass all permission checks" implies no interactive prompts, but the trust dialog still appears on every launch.
This is separate from issue #25503 (which covers the bypass permissions mode dialog / skipDangerousModePermissionPrompt). The workspace trust prompt is a distinct security boundary that the flag doesn't cover despite the documentation suggesting otherwise.
Steps to Reproduce
- Launch Claude Code with
--dangerously-skip-permissions from a directory that does not contain a .git folder:
cd ~
claude --dangerously-skip-permissions
- The workspace trust prompt appears:
Quick safety check: Is this a project you created or one you trust?
❯ 1. Yes, I trust this folder
2. No, exit
Note: The trust prompt only appears in directories without a .git folder. If you launch from a git repository (e.g. a project directory), the prompt does not appear. This suggests the trust check is tied to whether the directory is a git repo, not whether the user has opted into bypassing permissions.
Expected Behavior
Either:
- The flag should skip the workspace trust prompt — the user has already explicitly opted into bypassing all permission checks, making a secondary trust confirmation redundant, OR
- The help text should be corrected to state that workspace trust is not covered, e.g.: "Bypass all permission checks except workspace trust."
Option 1 is preferred — if a user passes a flag literally named "dangerously skip permissions", they've accepted all risks.
Current Behaviour
The workspace trust prompt appears regardless of the --dangerously-skip-permissions flag when launching from a non-git directory. There is no CLI flag or persistent setting to skip it (trust decisions also don't persist across sessions — see closed issues #9113, #21283).
Environment
- Claude Code version: 2.1.56
- OS: Linux (Ubuntu)
- Shell: bash
Description
The
--dangerously-skip-permissionsflag's help text states:However, the workspace trust prompt ("Quick safety check: Is this a project you created or one you trust?") is not bypassed by this flag. This is misleading — "bypass all permission checks" implies no interactive prompts, but the trust dialog still appears on every launch.
This is separate from issue #25503 (which covers the bypass permissions mode dialog /
skipDangerousModePermissionPrompt). The workspace trust prompt is a distinct security boundary that the flag doesn't cover despite the documentation suggesting otherwise.Steps to Reproduce
--dangerously-skip-permissionsfrom a directory that does not contain a.gitfolder:Note: The trust prompt only appears in directories without a
.gitfolder. If you launch from a git repository (e.g. a project directory), the prompt does not appear. This suggests the trust check is tied to whether the directory is a git repo, not whether the user has opted into bypassing permissions.Expected Behavior
Either:
Option 1 is preferred — if a user passes a flag literally named "dangerously skip permissions", they've accepted all risks.
Current Behaviour
The workspace trust prompt appears regardless of the
--dangerously-skip-permissionsflag when launching from a non-git directory. There is no CLI flag or persistent setting to skip it (trust decisions also don't persist across sessions — see closed issues #9113, #21283).Environment