in the chat, when executables are executed, the text from the AI on AI based approval should be availble through a little robot icon that sits beside the command execution (beside the "bash" text). when hovering over it, the text the AI sent for the harmfulness check should be shown. old sessions don't have agent reasons and so don't show that icon, same with heuristic sessions. only when an AI justification is recorded is that icon shown. AI based execution confirmation will create a record in the chat about the reason of the AI.
in the chat, when executables are executed, the text from the AI on AI based approval should be availble through a little robot icon that sits beside the command execution (beside the "bash" text). when hovering over it, the text the AI sent for the harmfulness check should be shown. old sessions don't have agent reasons and so don't show that icon, same with heuristic sessions. only when an AI justification is recorded is that icon shown. AI based execution confirmation will create a record in the chat about the reason of the AI.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
in the chat, when executables are executed, the text from the AI on AI based approval should be availble through a little robot icon that sits beside the command execution (beside the "bash" text). when hovering over it, the text the AI sent for the harmfulness check should be shown. old sessions don't have agent reasons and so don't show that icon, same with heuristic sessions. only when an AI justification is recorded is that icon shown. AI based execution confirmation will create a record in the chat about the reason of the AI.
implemented