[FEATURE] Every negative answer is at least 3. 2 for "always" or "no" sucks

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 claude asks me to approve something I get a:

1. yes
2. always allow <thing>:*
3. no

|| or || maybe I get:

1. yes
2. no

so 2 can mean : yes I really trust claude or no, I don't trust. This overload sucks when people have to use muscle memory to do this. I consistently hit the wrong key. don't overload 2. to be negative and positive. just set 3 to be negative always.

Proposed Solution

Do this:

1. yes
2. always yes...
3. no

|| or ||

1. yes

3. no

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_