Similar commands should be approvable for the whole session

[petrroll]

Describe the feature or problem you'd like to solve

Using CLI on Windows (didn't try wsl yet), when it searches via grep-like, one needs to approve each search individually

Proposed solution

Option to approve a command and all similar commands (categorized by LLM?) for current session and/OR globally forever.

Example prompts or workflows

No response

Additional context

No response

[williammartin]

Hey @petrroll thanks for opening the issue. On unix, my expectation is that grep should offer session approval and then be done. However, two things might be happening here:

1. Windows (non-WSL) might behave differently
2. Often the model seems to want to write redirect stderr from grep like: grep -r "foo" . 2>/dev/null, and right now we require approval every time there is a write redirection due to the risk (and not having solved the general case nicely yet)

Maybe you could keep an eye out and see if you're hitting the second case?

[petrroll]

2. doesn't seem to be the case, the commands as e.g.:

 ✓ Search for large request protector mentions in release notes
   $ Get-ChildItem -Path "E:\Source\**REDACTED**\Release-Notes" -Recurse -Include "*.md" |
   Select-String -Pattern "large **REDACTED**" -CaseSensitive:$false -Context 2,2
   ↪ 71 lines...

 ● Now let me search for mentions about logging URL or not logging URL:

 ✓ Search for logging URL mentions in release notes
   $ Get-ChildItem -Path "E:\Source\**REDACTED**\Release-Notes" -Recurse -Include "*.md" |
   Select-String -Pattern "logging.***REDACTED**" -CaseSensitive:$false -Context 2,2
   ↪ 99 lines...

[SteveSandersonMS]

@petrroll Can you let us know which command it's asking for permission to run, or paste in the confirmation request it shows? I'm not certain whether it's really asking for permission to run a command here, or if it's actually asking for permission to access files in a directory you haven't yet approved.

My suspicion is that maybe your -Pattern values are being detected as paths.

[petrroll]

... and so on

[petrroll]

It definitely seems plausible.

[examon]

This is supported. The permission dialog offers a "Yes, and approve for the rest of this session" option, which covers subsequent invocations of the same command identifiers during the current session. For a blanket bypass, the /allow-all command (available since v1.0.12) grants session-wide approval for all tools. If you believe this still does not address your scenario, please feel free to reopen this issue.