Visual distinction for high-consequence permission prompts

Resolved 💬 3 comments Opened Feb 11, 2026 by ethan-glover Closed Feb 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When using permission settings that require approval for commands like git commit and git push, the approval prompt looks identical to prompts for read-only commands like git status.

Proposed Solution

It would be helpful if high-consequence commands (commit, push, delete, publish) had a more prominent visual treatment — different color, icon, or larger warning — so they stand out from routine approvals.

This is especially useful for less experienced developers who may not immediately recognize which commands are safe vs. irreversible.

It might also be helpful to remove the 'always allow' settings for certain commands, so accidentally committing and pushing aren't a consequence of accidentally clicking 'always allow'

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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