Repository navigation
Bug: error: unknown option '--no-warnings' noise in terminal #1446
Description
Describe the bug
🐛 Bug: error: unknown option '--no-warnings' noise in terminal
Product: GitHub Copilot CLI
Version: 0.0.409 (WinGet install)
Binary: C:\Users\neilghosh\AppData\Local\Microsoft\WinGet\Packages\GitHub.Copilot_Microsoft.Winget.Source_8wekyb3d8bbwe\copilot.exe
Environment
┌─────────────┬───────────────────────────────────────────────────┐
│ Key │ Value │
├─────────────┼───────────────────────────────────────────────────┤
│ OS │ Windows NT 10.0.26200.0 │
├─────────────┼───────────────────────────────────────────────────┤
│ Node │ v22.21.0 │
├─────────────┼───────────────────────────────────────────────────┤
│ Git │ 2.53.0.windows.1 │
├─────────────┼───────────────────────────────────────────────────┤
│ Dotnet │ 8.0.418 │
├─────────────┼───────────────────────────────────────────────────┤
│ CLI Version │ 0.0.409 (WinGet), 0.0.394 (npm — stale, not used) │
├─────────────┼───────────────────────────────────────────────────┤
│ Session ID │ 568fe8d3-fc78-435b-84da-6c8307946b8f │
└─────────────┴───────────────────────────────────────────────────┘
Repro
The error error: unknown option '--no-warnings' appears intermittently in the terminal during agent execution. --no-warnings is a Node.js flag, but it's being passed to git (confirmed: git
--no-warnings produces the exact same error).
Root Cause (suspected)
The Copilot CLI binary (compiled Go/Node hybrid, 114MB) likely sets NODE_OPTIONS=--no-warnings internally, which leaks into child git process invocations. Git doesn't recognize this flag and
prints the error to stderr.
Impact
Cosmetic only — no functional impact. Creates noise in the terminal output during agent operations.
Workaround
$env:NODE_OPTIONS = ""
Affected version
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response
Activity
andyfeller commentedon Feb 13, 2026
@neilghosh : Thank you for raising this issue and apologies for the frustration this must be causing! 🙇
I believe this is a duplicate of #1399 which I've merged in a fix yesterday that should be released later today. 🤞
vzarytovskii commentedon Feb 25, 2026
Still seeing it in
v.0.0.417, not the--no-warningsone, but about--help.vzarytovskii commentedon Feb 26, 2026
Just hit today morning (v419).
ianchak commentedon Mar 2, 2026
The issue is still there in v420 and it's really annoying.
binli commentedon Mar 18, 2026
Same for me, I met this issue on nixos unstable.
$ NODE_OPTIONS="" copilot
error: unknown option '--no-warnings'
Try 'copilot --help' for more information
$ copilot --version
GitHub Copilot CLI 1.0.4.
Run 'copilot update' to check for updates.
$ copilot update
error: unknown option '--no-warnings'
Try 'copilot --help' for more information.
x10an14 commentedon Mar 18, 2026
Adding 👍 to post above to signify "this happens to me too" --^
mvillafuertem commentedon Mar 27, 2026
Workaround
fix: remove copilot wrapper from Docker image, fix NODE_OPTIONS leak
fix: remove copilot wrapper from Docker image, fix NODE_OPTIONS leak
patniko commentedon Oct 26, 2026
Thanks for the report. We've shipped fixes in this area since this was filed (most recently in Copilot CLI v1.0.83), and we believe this may now be resolved. Could you retest on the latest release (Copilot CLI v1.0.103) and let us know whether you still see it? If we don't hear back in a couple of weeks, we may close this issue — you can always reopen it.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.