[FEATURE]

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 a command run via ! triggers an interactive prompt (a password, a [y/N], an SSH passphrase), the input field is the same box you type every chat message into
— no color shift, no lock icon, no "you are now entering a shell prompt" framing. For a password prompt specifically, that ambiguity is exactly the wrong place to be ambiguous. A distinct visual state
for "this keystroke is going to a running command's stdin, not to the model" is the obvious mitigation, and it's not there.

There needs to be a UI affordance, to mitigate this potential security issue - you're tactily training users to trust the that they can paste confidential information into the Claude Code text prompt. This is the very definition of a bad UI pattern.

Proposed Solution

A color shift, a box change, a lock icon, a warning "you are now entering a shell prompt" framing.
Something, anything

Alternative Solutions

You run your commands in a separate terminal, copy and paste output.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_