You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Insiders Feedback: Disable interactive PR creation form #3470
Second this! The agent running on auto mode now gets stuck. It opens up a form, but doesn't realize when I have submitted any action on it, and is just stuck "thinking" until I manually stop it.
I'm using Visual Studio Code's github copilot extension and this MCP update has scuppered productivity.
It'll display a poorly-dimensioned dialog within the chat window, making it hard to see what's going on, and if you do "press the button", nothing proceeds - the AI just hangs, like it's still waiting.
Worse, if you later scroll back up to see your history, up pops the MCP dialog again within the chat history, asking you to do it again.
So it seems that it "doesn't notice" when you push "ok" (or whatever the JFDI button is) and so it tells AI it needs to keep waiting for the human and it keeps on asking the human.
IME a good workaround is to instruct CoPilot to use the gh command-line instead of the MCP.
Activity
HaveSpacesuit commentedon Oct 13, 2026
Second this! The agent running on auto mode now gets stuck. It opens up a form, but doesn't realize when I have submitted any action on it, and is just stuck "thinking" until I manually stop it.
SamR232 commentedon Oct 16, 2026
This is now broken again, same as issue as above^.
Peter-Darton-i2 commentedon Oct 19, 2026
I'm using Visual Studio Code's github copilot extension and this MCP update has scuppered productivity.
It'll display a poorly-dimensioned dialog within the chat window, making it hard to see what's going on, and if you do "press the button", nothing proceeds - the AI just hangs, like it's still waiting.
Worse, if you later scroll back up to see your history, up pops the MCP dialog again within the chat history, asking you to do it again.
So it seems that it "doesn't notice" when you push "ok" (or whatever the JFDI button is) and so it tells AI it needs to keep waiting for the human and it keeps on asking the human.
IME a good workaround is to instruct CoPilot to use the
ghcommand-line instead of the MCP.victor-variu-tss commentedon Oct 19, 2026
while vibe coders may like it, developers who run autonomous workflows certainly don't - make it optional please