github / github/copilot-cli

Copilot always tries unix command before PowerShell

Open
#689 0 comments 9 reactions 0 assignees View on GitHub
area:platform-windows area:tools
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

### Describe the bug

I'm running copilot-cli on Windows in PowerShell.
I have the following in my `custom-instructions.md` file:

```markdown
- Assume that you are running in a Windows environment.
- Any shell or terminal commands/syntax should be PowerShell native commands and any paths should use Windows-style backslashes.
- DO NOT use Unix/Linux-style commands or paths unless explicitly instructed otherwise.
```

However, copilot almost always tries to use Unix/Linux shell commands like grep, head, wc, etc, before trying PowerShell.

Example:

> ✔ List build errors by file
> $ dotnet build --nologo --tl:off 2>&1 | grep "\.cs(" | head -20
> └ 7 lines...
>
> ✔ List build errors by file
> $ dotnet build --nologo --tl:off 2>&1 | Select-String "\.cs\(" | Select-Object -First 20
>

### Affected version

0.0.365

### Steps to reproduce the behavior

_No response_

### Expected behavior

Copilot CLI understanding that it is running in a Windows PowerShell environment and using PowerShell command instead of Unix/Linux style commands

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.