What happened?

I create an extension to accept/reject the tool calls. Upon having the confirmation, often the tool call shown before is nicely formatted and way better than displaying the raw arguments. For example in this screenshot, the details in the confirmation are garbage while the "write" block before is nice and sufficient (except it is collapsed):

So I tend to simplify the prompt for some tool calls and just rely on what is displayed before (not yet done in the screenshot).

The issue is for big changes, that need CTRL+O to be expanded, like in the screenshot. It does not work while waiting for the answer. So I can't see all the details when it asks me to confirm a big change.

Steps to reproduce

1. Create an extension that for any tool call request a confirmation and /reload to enable it,
2. ask for a tool call to write a big file at once,
3. upon confirmation, use CTRL+O to show the details of the write -> CTRL+O does not work

Expected behavior

CTRL+O is expected to work

Currently, I deal with it by automatically expanding before the confirm, and set the expansion back to its previous state after confirmation. But it kind of blow up every time it does that (because there is a lot to display in the discussion) so it is not nice, and it does it every time while it is only required for big ones. For example read never needs it yet it blows up the same. This strategy looks more like a cheap trick than a proper fix, so I would expect instead that CTRL+O can be used while waiting for the confirmation if possible.

Version

0.74.0