Unclear When a session runs without the classifier is not established.
What
In auto mode, a safety check called the classifier normally decides whether a tool call may run. When a permission prompt is shown in its place (inPlaceOfClassifier set to true), the prompt now behaves more cautiously.
- The Bash, file and PowerShell permission dialogs start with focus on reject instead of accept.
- The "No" option comes first and the option numbers are hidden (
hideIndexes). - Only one-time answers are offered, with no "always allow" option. If you allow, any permission rules the prompt would have saved are dropped, so nothing is remembered.
- "No" is also preferred when the dialog refuses an input.
- The reason row gets a limit on how many lines it takes, in the PowerShell and generic tool prompts.
- Such a prompt is treated like a one-time-only prompt and cannot be approved automatically.
- A new result reports that no classifier ran: model "auto mode", unavailable, reason "No classifier runs for this session".
Where inPlaceOfClassifier gets set was not found.
Why
Pressing Enter on one of these prompts now rejects the action rather than approving it, and no lasting permission can be saved from it. Read the prompt before you approve.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
When a session runs without the classifier is not established.