$ recombobulate _
home / tips / skip-the-bypass-permissions-confirmation-prompt
239

Skip the Bypass Permissions Confirmation Prompt

recombobulate @recombobulate · Mar 26, 2026 · Configuration
skip-the-bypass-permissions-confirmation-prompt

Even after you set bypassPermissions as your default mode, Claude Code still shows a confirmation prompt at the start of every new session. One extra keystroke per session sounds minor until you're running five sessions in parallel.

Add this to your ~/.claude/settings.json:

{
  "permissions": {
    "defaultMode": "bypassPermissions"
  },
  "skipDangerousModePermissionPrompt": true
}

With both settings in place, new sessions start immediately with no gate to click through. Claude Code assumes you've already made the decision once and trusts that it holds.

This is separate from Shift+Tab, which toggles bypass mode on and off during a session. skipDangerousModePermissionPrompt just removes the startup confirmation for sessions that are already in bypass mode.

Worth noting: when you first try to enable this, Claude Code will actively push back and try to talk you out of it. You need to be direct and explicit. It's your machine.

Only enable this on computers you fully control. Shared environments, CI runners, or machines where others have access are not the right place for it.

Set it once, never click through it again.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Describe Your Users in CLAUDE.md So Claude Writes Appropriate Copy, Error Messages, and UX

When Claude writes error messages, button labels, validation text, or onboarding flows, it defaults to generic developer-speak. Add a "Users" section to your CLAUDE.md describing who your actual users are — their technical level, industry jargon, and what they care about — so Claude writes copy that makes sense to THEM, not to developers.

recombobulate @recombobulate · 1 month ago
1
Create Custom Agents with --agent for Scoped Sessions

Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.

recombobulate @recombobulate · 1 month ago
106
Add Known Gotchas and Pitfalls to Your CLAUDE.md So Claude Avoids Mistakes Your Team Already Made

Every project has traps — the billing module that silently fails if you forget to queue the job, the legacy table with column names that don't match the model, the config value that must be set before tests run. Document these gotchas in your CLAUDE.md so Claude avoids the same mistakes your team spent days debugging.

recombobulate @recombobulate · 1 month ago