When Duo runs a command that the output is displayed through a pager, it requires manual interaction with the terminal
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Duo Agentic chat inside VSCode can get stuck when an approved command runs, depending on the output it produces. Output through a pager, from commands like man and git log , will require the user to press Q to return to the regular shell prompt. If the user does not press Q in the terminal window being used by Duo, Duo will get stuck indefinitely.
Steps to reproduce
- Using the VSCode plugin, Ask Duo Agentic chat something related to the changes in the current branch, suggest it to discover the changes using git, to compare with the master branch.
- Duo will request approval to run something, like
git log, approve it. - Duo will get stuck indefinitely, unless you find the terminal window and press
Q.
What is the current bug behavior?
Duo won't get the prompt back when a command it runs outputs through a pager.
What is the expected correct behavior?
Duo should get the prompt back after the output of the command is seen, so it can move forward with the next steps of the conversation.
Possible fixes
Skip the pager entirely by piping commands with | cat or disable the pager, whatever is the most universal choice.