[BUG] VS CODE Extension no longer allows --dangerously-skip-permissions
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Previously the vs code extension would launch with the claude command. in order to run --dangerously-skip-permissions we would have to close the terminal, open it back up and run the command with this flag. however now the extension no longer runs the claude command in the terminal, it does it internally. so there is no way to allow us to skip permissions. so this makes it so that even with edit automatically we still have to approve pretty much every tool call request. if this is permanently inaccessible then there should be a setting to allow this such that we can run without having to give permissions to every tool.
What Should Happen?
We need a way of being able to run claude code in the VS CODE extension without permissions. We are no longer able to because of the architectural design
Error Messages/Logs
Steps to Reproduce
open the vs code extension. no settings allow us to disable permission checks
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.0
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
75 Comments
---
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Increase priority for this ticket, since with the newly updated Claude Code VSCode extension, the workaround with Ctrl+C and running 'claude --dangerously-skip-permissions' it does not work anymore. I've tried setting an alias in zshrc, but it does not work since extensions are not loading up the shell, I've tried adding this flag to ~/.claude/settings.json, it did not work.
+1
+1
also,
i use this extension in cursor, and i wish to have a solution there also
same
+1
Adding some additional thoughts..
There are other small affordance differences that are not keyboard focused, a single click anywhere doesn't give the textbox focus, escape button doesn't work when modals pop-up, less insight into progress, no ctrl-o, no thinking mode hooks that I can see beyond config etc.. in addition to no option to dangerously-skip-permissions.
Love using this but for now gonna head back to the CLI.
What worries me more is that this feels “on purpose”, which makes me worry directionally. Let’s not slow things down. There’s plenty of other guardrails to you use in your repo. One of the best things about Claude code was that it was much like a CLI: plenty of config and everything out in the open.
+1
same problem, i really hope this isn't intention
+1
+1
+1
+1
+1
+1
+1
+1. I can't use this until I have a workaround here
@max-winderbaum yeah i just went to using claude code directly in the terminal. Doesn't have any of these issues
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
++
+2 (please!!)
This is so frustrating
+1
+1
+1
+1
Claude Code just became totally useless for me, now changing to Codex. I WAS fan of claude code. Done!
1, allow, 1 allow, 1, allow.... No way!!!
+1
+1
+1
+1
+1
Has anyone found a workaround for this yet, aside from running it in the terminal? Or is it something only Anthropic can fix?
+1
No workaround that I can find, other than using the terminal. The native extension is so close, but without this feature, I'm sticking to the CLI.
Stopped using the extension entirely now, total dealbreaker.
+1
+1
+1
Rather than just +1'ing this (which I support), I'll add a little color on how I use the product. I very frequently operate Claude Code via the extension to do some work for me and then tab away to some other task. If I remain present, the _extremely_ frequent permission prompts are annoying, but if I tab away, they're actively disruptive since I return later only to find nothing completed.
I totally respect and appreciate the aim to add safety into the product, but I think the controls around the intended permission tolerance are missing. Do I want to give Claude permission to use
rm? Maybe, maybe not; I'm glad you asked. Do I want to give it permission to search "linear sdk 2025" on the web? Yes; please stop asking me. But keeping an allow-list of tools is also untenable. I trust the LLM to make a judgement call on what could be dangerous or not, and if there's nuance, I can add it to my CLAUDE.md or some other config location.tl;dr: This isn't just missing polish. It's actively disruptive and really breaks the experience of the extension vs CLI.
Please add this feature to Claude code extension for VSCode. Thank you.
Even better than the YOLO approach is to use a Claude development container, which creates a limited-access Docker container for development. You then run “Reopen in Container" in VS Code, and run Claude Code inside the container. Since your codebase is the only content inside the container, this is all Claude has access to… and YOLO no more… 🙂
It looks like @zeke has opened a proper feature request for this. (Thanks!) So hopefully this is on the @anthropics radar.
+1
把这个放到 插件同目录("C:\Users\your-user-name\.vscode\extensions\anthropic.claude-code-xxxxxxxxxx")下,保存成 bat 文件,然后执行:
+1 Cant use the extension w/o this feature.
+1 The extension is unusable without it!
Won't touch CC extension without it.
This was seriously slowing me down so much i build a patcher to fix the issue.
Find it here:
https://github.com/jimmy927/claude-code-extension-patcher
need this NOW
MUST have this
Looking into this now!
This feature has been added and should be out before the end of the week. I'll follow-up with instructions on how to enable when it's out!
There are SO MANY unskippable things that Claude confirms on...pgpassword,
mkdir, just...do it already, dude! I trust you, Claude.
On Thu, Oct 23, 2025, 11:34 JB @.***> wrote:
This should be available in 2.0.26!
You will first need to enable the
Allow Dangerously Skip Permissionsoption in preferences (you can open it up withGeneral Config (VScode)in the extension's command menu/). Once you've toggled the option, you should be able toshift+tabinto the bypass permissions mode.Please give it a spin when you get a chance! Closing this issue out, but feel free to file another issue if you encounter problems with it
Format my hard drive! Right my ex's and tell them I want to get back
together! Just don't make me confirm!
On Thu, Oct 23, 2025, 19:43 JB @.***> wrote:
do you realize how much time ive spent using claude to patch
--dangerously-skip-permissionsafter every update!? lol, glad its finally a feature.can you now please allow further customization to the status line? like git branch, the context window, and other features popular in the terminal based CC affords?
or better yet, just fix the schizo terminal behavior where I feel like im plugging into the matrix and i have no need for the extension 👍
what about those who uses CC extension in cursor? how do we do that?
You should be able to access the same settings in Cursor
You can click the settings Editor four times and it changes too just for
this editor.
On Sat, Nov 1, 2025, 03:32 Bomin Zhang @.***> wrote:
Or just use Shift+Tab to cycle thru the modes. Easy peasy.
Is there a way to make a new window/session start with "Bypass permissions" ?
i start new sessions all the time and need to constantly toggle to "Bypass permissions" - its tedious.
@jimmy927 we just added this option to the latest version, it should be available inside
/General Configas Initial Permission ModeGREAT! which version will it be in ?
Solved in 2.0.35
<img width="1274" height="827" alt="Image" src="https://github.com/user-attachments/assets/2ac1f76e-7158-4899-9abc-f5cdfd32f39b" />
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.