-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Copilot-CLI eats STDIN when it shouldn't #3464
Copy link
Copy link
Open
Labels
area:input-keyboardKeyboard shortcuts, keybindings, copy/paste, clipboard, mouse, and text inputKeyboard shortcuts, keybindings, copy/paste, clipboard, mouse, and text inputarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
Metadata
Metadata
Assignees
Labels
area:input-keyboardKeyboard shortcuts, keybindings, copy/paste, clipboard, mouse, and text inputKeyboard shortcuts, keybindings, copy/paste, clipboard, mouse, and text inputarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
Type
Fields
Give feedbackNo fields configured for Bug.
Describe the bug
copilot plugin listconsumes STDIN when it shouldn't.Affected version
GitHub Copilot CLI 1.0.51.
Steps to reproduce the behavior
Do this, and then immediately start typing while it sleeps:
Whatever you type will - after the command finishes - appear on the next command line. Now do this and again start typing immediately while it sleeps:
Whatever you type will not appear on the command line, it gets eaten by copilot.
Expected behavior
copilot plugin list(and other similar commands of course) aren't interactive and so shouldn't read STDIN.Additional context
Observed on Mac OS 15.7.2.
This is a problem when you run
copilot plugin listin a script. I have it in my standard shell startup scripts to prompt me to install my favourite plugins if they're not available.As a work-around - and this proves that
copilot plugin listreally doesn't need to read STDIN - you cancopilot plugin list < /dev/null.