Pasting a build error is interpreted as attempting to execute a command #1668
Description
Describe the bug
My scenario is that when getting a build error from a CI or other log or something, I just like to paste in the build error to Copilot and it helps understand and resolve. At times the log error starts with a unix-style path like /user/name/foo/project/bar/logs/foo.swift:34-43
Pasting this into CLI results in "cannot execute command"
Other Copilot clients interpret and start working. If I prepend this with any text it's fine, but it is different than other clients like VSCode which just starts going to town.
And what is weird is other 'commands' in the CLI (like ls) are not interpreted as commands but as text to reason.
Affected version
0.0.417
Steps to reproduce the behavior
- Paste an error set of log output that looks like unix command paths
Expected behavior
It is treated as a prompt to solve just like anything else
Additional context
No response