{{ message }}
Repository navigation
[Bug] Chat hangs after running a terminal command in Agent mode #375
Description
Environment
- OS: Windows 11
- Eclipse Version: 2026-06 (4.40.0)
- Plugin Version: 0.20.0.202607100822
Describe the bug
Chat hangs after running a terminal command in Agent mode. After the terminal command finishes copilot does not continue with the agent job.
To Reproduce
Steps to reproduce the behavior:
Run a prompt in agent mode that requires a terminal command such as mvn or git to be executed.
Command runs in a terminal window in eclipse and finishes (i.e. the PS> line appears after the command execution)
In the copilot chat window the text has Running run_in_terminal tool but than hangs (see screenshot)
Expected behavior
Prompt should continue
Screenshots
Activity
briane80 commentedon Jul 28, 2026
Happening every time for me - here i got it to run mvn -version and it has hung.
briane80 commentedon Jul 28, 2026
Also hung with a simple echo hello command
briane80 commentedon Jul 28, 2026
For context agent mode terminal commands worked ok previously for me - probably in version 0.19. I haven't used agent mode for a long time but tried today and started getting this hung chat issue.
xinyi-gong commentedon Jul 29, 2026
briane80 Thank you for reporting this issue and for providing the screenshots.
Could you please share the Eclipse log file (/.metadata/.log) after reproducing the issue, or any relevant entries from the Error Log view?
I noticed that the PowerShell prompt shown in the terminal is PS> rather than the usual prompt containing the current path, such as PS C:...>. PowerShell may display PS> as a fallback when its prompt function fails. Since Copilot relies on PowerShell prompt integration to detect when a command has completed, this could explain why the command finishes but the agent continues waiting.
One possibility is that PowerShell is running in a restricted environment, such as ConstrainedLanguage mode. Could you run the following command in the same terminal session opened by Copilot and share the output?
$ExecutionContext.SessionState.LanguageModeThis will help us confirm whether the PowerShell environment is preventing the prompt integration from running correctly.
briane80 commentedon Jul 29, 2026
Thanks for the reply and upoming fix - I see you were able to replicate. I can confirm I am running in ConstraintedLanguage mode -
PS>$ExecutionContext.SessionState.LanguageMode
ConstrainedLanguage
xinyi-gong commentedon Jul 29, 2026
briane80 Thanks for confirming! Once a stable or nightly release containing this fix is available, I’ll let you know so we can check whether the issue still reproduces.