Summary
Authorization requests are easy to miss in the terminal UI because they are not visually prominent enough when Atman pauses for user approval.
Problem
When a tool call requires authorization, the approval request can blend into surrounding terminal output. If the user is looking away briefly or the output is busy, the request may remain unnoticed and the workflow appears stalled.
Expected behavior
Authorization requests should be clearly distinguishable from normal output and immediately draw attention until they are handled.
Possible improvements
- Use a prominent, persistent banner or panel for pending authorization requests.
- Apply a strong, consistent color/style with a clear
AUTHORIZE or ACTION REQUIRED label.
- Show the affected tool, target, and risk level in the prominent prompt.
- Consider an optional terminal bell or desktop notification.
- Keep the pending request visible until the user approves, denies, or defers it.
Environment
Summary
Authorization requests are easy to miss in the terminal UI because they are not visually prominent enough when Atman pauses for user approval.
Problem
When a tool call requires authorization, the approval request can blend into surrounding terminal output. If the user is looking away briefly or the output is busy, the request may remain unnoticed and the workflow appears stalled.
Expected behavior
Authorization requests should be clearly distinguishable from normal output and immediately draw attention until they are handled.
Possible improvements
AUTHORIZEorACTION REQUIREDlabel.Environment