Software & DevOpsDone with GitHub Copilot Jun 1, 2025
Run terminal commands with Copilot agent mode
Users report the agent sometimes fails to read terminal output and may undo correct code; workarounds include switching shells.
- What They Did
- In a GitHub community thread, a user running Copilot agent mode in VS Code (launched from WSL) saw it miss terminal output or never register that a command had finished. Commenters shared workarounds: pressing Enter in the terminal, redirecting output to a file for the agent to read, adding instructions to copilot-instructions.md, and switching to plain bash or removing prompt themes like Powerlevel10k.
- How It Went
- A GitHub engineer traced it to old Powerlevel10k versions and recommended updating them, with VS Code fixes planned. Many users, including on bare bash and Windows, still reported hangs and the agent undoing correct code.
- Worth Knowing
- Wasted agent loops burn premium requests; updating Powerlevel10k, or using a minimal shell or prompt for the agent, is the most-cited fix, though some workarounds failed for others.
Try it yourself with GitHub Copilot
In my project at [path], run [build or test command] in the terminal and fix any failures. If you can't read the terminal output, tell me instead of guessing, and don't change code that is already working. Stop when the command passes, and give me a list of every file you changed.
Do this with a skill.
These SkillShop playbooks do this exact job.