-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Unnecessary directory access prompts #1110
Copy link
Copy link
Closed
Labels
area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictionsTool approval, security boundaries, sandbox mode, and directory restrictionsarea:platform-windowsWindows-specific: PowerShell, cmd, Git Bash, WSL, Windows TerminalWindows-specific: PowerShell, cmd, Git Bash, WSL, Windows Terminal
Description
Metadata
Metadata
Assignees
Labels
area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictionsTool approval, security boundaries, sandbox mode, and directory restrictionsarea:platform-windowsWindows-specific: PowerShell, cmd, Git Bash, WSL, Windows TerminalWindows-specific: PowerShell, cmd, Git Bash, WSL, Windows Terminal
Type
Fields
Give feedbackNo fields configured for Bug.
Describe the bug
Bug is in how CLI logic evaluates which files/dirs are being accessed as a result of responding to user prompts.
Case described in the "steps to reproduce" presents a situation where CLI was asking the user to allow directory access to directories that do not exist and could not even be valid.
Affected version
0.0.343 Commit: 5847051
Steps to reproduce the behavior
I asked copilot CLI the following:
"there is a special C# attribute placed on methods and classes related with error information processing. which one it is?"
As part of "thinking", copilot CLI performs evaluation of relevant files, often using the pattern similar to:
That is ok, but then it interactively prompts the user for directory access to "directory" matching the value of the Select-String pattern which is logically incorrect.
Expected behavior
Not be prompted for directory access.
Additional context