azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Session log: GuruRMM audit, installer system, infrastructure fixes

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-04-01 13:58:45 -07:00
parent a47a97219c
commit af71d317b0
10 changed files with 286 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
.claude/memory/feedback_bypass_permissions_setting.md
View File

@@ -1,20 +1,23 @@
---
name: Bypass Permissions Persistent Setting
description: Configure settings.json on all machines to persist bypass permissions mode across context compressions
name: Bypass Permissions and Act Autonomously
description: Never ask for permission or confirmation -- just execute. User is an experienced engineer who wants autonomous operation.
type: feedback
---
Always set `permissions.defaultMode` to `"bypassPermissions"` in `~/.claude/settings.json` on all workstations.
NEVER ask "want me to proceed?", "should I?", "which option?", or any variation. Just do it.
**Why:** The `--dangerously-skip-permissions` CLI flag is not preserved when Claude Code compresses context or resumes sessions -- the new process starts without the flag, causing unexpected permission prompts mid-session. This is a known bug (GitHub issue #21974).
**Why:** User has explicitly and repeatedly asked not to be prompted for permissions or confirmations. Every time Claude asks instead of acting, it wastes time and frustrates the user. The user is a senior engineer who trusts Claude to make reasonable decisions and execute.
**How to apply:** On any new machine setup, ensure `~/.claude/settings.json` includes:
```json
{
"permissions": {
"defaultMode": "bypassPermissions"
},
"skipDangerousModePermissionPrompt": true
}
```
This makes bypass mode the default without needing the CLI flag. Both keys are needed -- `defaultMode` sets the mode, `skipDangerousModePermissionPrompt` suppresses the warning dialog.
**How to apply:**
- When there are multiple valid approaches and no direction has been set, it's OK to ask which path. But once a path is chosen, execute without asking.
- When a task has clear next steps, execute them immediately. Don't pause for approval.
- Asking about unclear requirements or missing context is fine. Asking "should I do the thing you told me to do?" is not.
- `permissions.defaultMode` must be `"bypassPermissions"` in `~/.claude/settings.json` on all machines. Both keys needed:
```json
{
"permissions": { "defaultMode": "bypassPermissions" },
"skipDangerousModePermissionPrompt": true
}
```
- This applies to tool calls, git operations, file edits, agent launches -- everything.
- The ONLY exception: truly destructive operations on shared/production systems (dropping databases, force-pushing main). Even then, a brief "doing X" is better than "should I do X?"