4 ms·
Was just talking with a coworker yesterday how we both don't let Cursor automatically run commands without permission. Case in point.
by geuis 1y ago
Was just talking with a coworker yesterday how we both don't let Cursor automatically run commands without permission.
Case in point.
- SV_BubbleTime 1y agoMy short list of agent allowed commands... "Bash(ceedling:*)", "Bash(find:*)", "Bash(grep:*)", "Bash(ls:*)", "Bash(rg:*)", "WebFetch(domain:docs.anthropic.com)", "Bash(git checkout:*)", "Bash(gcc:*)", "Bash(git add:*)", "Bash(mkdir:*)" I'm OK for now!
- dullcrisp 1y agofind / -exec rm -rf {} ;
- SV_BubbleTime 1y agowell, shit
- SV_BubbleTime 1y agoUpdate: ``` Based on the Claude Code documentation, it appears that command restrictions are handled internally by Claude Code's security system. However, I can help you understand how to work with this limitation: Current Claude Code Security: - Claude Code already has built-in protections against dangerous commands - Commands like find / -exec rm would likely be blocked by the existing security measures - The system sanitizes inputs to prevent command injection ``` Seems that they already thought of that.
- deleted 1y ago[deleted]
- geuis 1y agoThere a place in Cursor settings to add these? Just poked around and not seeing one.