Allow commands in session/workspace

[roblourens]

This difference just occured to me. In other tools I can allow them in the session or the workspace. For terminal commands, it only offers to change my settings. Allowing a command just for a session would be nice. I sometimes would like to allow something riskier for a certain task but I know that I don't want it in my settings

I actually don't know whether "session" is "chat session" or "window session", I think I want "chat session" but it might not work that way

[Tyriar]

@bpasero also asked for this, we could always allow that exact command line? Little worried about that drop down getting too crowded

[bpasero]

I would only show an entry for allowing the command in the session, with any command line.

[Tyriar]

@roblourens adding top (with safe args) in #260859, since head is already safe that would have made that auto approve.

I would only show an entry for allowing the command in the session, with any command line.

@bpasero by command line I mean there are different ways we could create a rule to auto approve it in the future. All sub commands and command lines are the 2 ways we offer for most commands:

The top one here is a lot riskier than the bottom one for example as npm i -g ... would be auto approved.

[bpasero]

Yeah good point, maybe we also wait a bit more on user feedback for this. Then, only taking the full command and arguments seems right for the session.

[Tyriar]

Separators are coming to the dropdown in #260891 which should help with readability if we do this