Skip to content

KoreanThinker/bypass-permission-never-stop

Repository files navigation

♾️ bypass-permission-never-stop

CI Release Security Scan npm version npm download License MIT Stars

Installer that adds bypass permission never stop mode to Claude Code's Shift+Tab cycle.

🎬 Live demo

bypass permission never stop mode demo

⚙️ How it works

  • With bypass permission never stop on, one submitted message is re-submitted repeatedly.
  • The loop continues while the Claude process and session are still active.

✨ Highlights

  • 🚀 One-command install
  • 🔁 Continuous re-submit loop mode
  • 🔄 One-command upgrade with upgrade/update
  • 🩺 One-command diagnosis with doctor
  • ♻️ Safe rollback with uninstall

Quick start

npx bypass-permission-never-stop

When prompted, type yes to install.

Rollback

npx bypass-permission-never-stop uninstall

Upgrade (best practice)

When a new package version is released, use upgrade instead of manual uninstall + install.

npx bypass-permission-never-stop@latest upgrade

Alias command:

npx bypass-permission-never-stop@latest update

Non-interactive mode:

npx bypass-permission-never-stop@latest upgrade --yes

upgrade restores the previous backup first, then applies the latest patch.

Doctor (diagnose + guided fixes)

Run diagnosis first when install/upgrade behavior looks wrong:

npx bypass-permission-never-stop doctor

What doctor does:

  • Runs target/signature/hook/backup consistency checks
  • Prints PASS/WARN/FAIL summary and next commands
  • Offers guided auto-fixes (restore/reinstall) with a single confirmation when inconsistent state is detected

What you should see

  1. Run claude
  2. Press Shift+Tab
  3. Confirm bottom mode text shows bypass permission never stop on

CI / non-interactive install

npx bypass-permission-never-stop --yes

Use this only when you intentionally want unattended install.

Sample prompt (one)

Use this once bypass permission never stop mode is enabled:

Mission: Continuously find and fix real bugs from Sentry, GitHub issues, and direct code exploration; after each fix, immediately start the next bug cycle.

Links

  • Troubleshooting: docs/TROUBLESHOOTING.md
  • QA details: docs/QA_REPORT.md
  • Changelog: CHANGELOG.md