XML code inside command is interpreted as a file

[laeubi]

Describe the bug

Copilot tried to execute this command

grep -n "</section>" /some/file | tail -20

this results in the cli ask me if copilot should be allowed to access /section directory (what does not exits)

this then seem to result in

✗ Execution failed: terminated

Affected version

0.0.358 Commit: f5a8b1e76

Steps to reproduce the behavior

Maybe ask copilot to analyze some XML and it wants to find a closing tag in the file...

Expected behavior

No detection of such path, copilot continues to work. As the path does not exits at all and I have no access to it either it might be good that even if copilot really tried to access the path the llm is simply informed that the path is not there and can't be accessed or created.

Additional context

No response

[laeubi]

A similar issue arise with spaces in file names (what is quite common in Windows e.g. C:\Program Files or C:\Users\My User Name) here copilot CLI then suddenly ask if I want to allow Copilot the non default directories: C:\Users\My, User, Name\the\actual\working\directory that is quite annoying as it is asked repeatable times and the directories obviously not exists.