Allow read-only bash commands in plan mode

Resolved 💬 6 comments Opened Dec 4, 2025 by paj80paj Closed Feb 27, 2026

Feature Request

Allow specific read-only bash commands to run without approval in plan mode.

Problem

Plan mode blocks all Bash tool usage, even clearly read-only commands like:

  • ls
  • git status
  • git log
  • npm list
  • tree

This forces users to either exit plan mode or use workarounds (Read/Glob/Grep tools) that don't cover all use cases.

Proposed Solution

Either:

  1. Read-only bash allowlist for plan mode - Let users specify bash commands that are safe during planning (e.g., Bash(ls:*), Bash(git status:*))
  2. Built-in safe command list - Hardcode common read-only commands as allowed in plan mode

Use Case

During planning, I often need to:

  • Check git status/log to understand current state
  • List directory contents with specific flags (ls -la)
  • Run npm list or similar to check dependencies
  • Use tree to understand structure

These are all non-destructive and useful for planning.

Current Workaround

Using Read/Glob/Grep tools, but they don't cover git commands, npm commands, or other CLI utilities.

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗