-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal Hangs in Agent Mode with "Running command in terminal…" #4814
Comments
Me too, same logs. I'm using:
Update: I tested it with bash instead of zsh and it worked |
These types of problems are likely due to lack of shell integration, notice that you don't have circles on the left of the terminal like this: This is probably the reason bash works fine. Note also there are known issues with powerlevel10k as well since they disable our shell integration explicitly in favor of ours (which we should handle gracefully). |
@Tyriar Thanks for you support Daniel! I have updated the powerlevel10k, the latest version improves the vscode integration and copilot in agent mode works. |
@argentinaluiz great to hear! |
Can we get the workaround instructions? I'm also using powerlevel10k Thanks! |
@kennyeni Follow the update command for oh-my-zsh in readme: https://github.com/romkatv/powerlevel10k?tab=readme-ov-file#how-do-i-update-powerlevel10k. Then, restart the terminal |
I have encountered a similar issue using zsh with oh-my-zsh but no powerlevel10k. Would appreciate any thoughts on how to fix. I did try verifying the $ZDOTHOME value, the bin executable path and all of those. |
@ShaiDiamant do you have a right prompt? I've seen that mess with our shell integration too. |
I didn't change the prompt and I only recently downloaded the VS Code Insiders, so I assume I should have the right prompt.. Also - it does trigger terminal commands, but kind of waits forever even after they finished running Edit: I guess there's some sort of delay with the integration availability.
Also, I noticed that if the agent tries to execute a command in the terminal, then I kill it, then the same chat tries to execute another command - it also hangs (I think it is waiting for response from the original terminal, but it no longer exists) Edit 2: |
Hi! I have a similar issue. I am using Powershell 7.5 and I have the terminal integration enabled, without decorations. It works for scripts that have an end, but seems like It can not read the output of the terminal while the script is running. I am not sure if this an issue but would be very useful if the copilot could read the output, stop the terminal if it sees errors, fix them and then run again. |
The updates may be bringing in romkatv/powerlevel10k@119e403 which forces p10k's shell integration to be enabled. |
The remaining fix here is going to be adding a section about updating p10k to the terminal shell integration and copilot docs: microsoft/vscode-docs#8082 |
@Tyriar Please note that this is not exclusive to p10k - it also happened to me before I started using p10k. p10k actually resolved this for me. |
@ShaiDiamant thanks, will try out using your setup too (oh-my-zsh/zsh-autosuggestions/pyenv/nvm) |
@Tyriar I think the actual causes were pyenv + nvm which significantly slowed the load of the terminal due to these commands in the ~/.zshrc:
|
2025-02-09 08:37:37.273 [info] Using the Electron fetcher.
2025-02-09 08:37:37.273 [info] Initializing Git extension service.
2025-02-09 08:37:37.280 [info] Logged in as sly01
2025-02-09 08:37:37.299 [info] Successfully activated the vscode.git extension.
2025-02-09 08:37:37.299 [info] Enablement state of the vscode.git extension: true.
2025-02-09 08:37:37.299 [info] Successfully registered Git commit message provider.
2025-02-09 08:37:38.054 [info] Got Copilot token for sly01
2025-02-09 08:37:38.147 [info] copilot token chat_enabled: true, sku: free_limited_copilot
2025-02-09 08:37:38.147 [info] GitHub.vscode-pull-request-github extension is not yet activated.
2025-02-09 08:37:38.155 [info] Registering default platform agent...
2025-02-09 08:37:38.749 [info] Fetched model metadata in 683ms 6b5ef23a-eb6e-44a1-8898-949c458f3c39
2025-02-09 08:37:38.779 [info] activationBlocker from 'languageModelAccess' took for 1113ms
2025-02-09 08:37:57.302 [info] message 0 returned. finish reason: [tool_calls]
2025-02-09 08:37:57.304 [info] request done: requestId: [54d84c3f-a60b-4599-afc7-dc5192482172] model deployment ID: []
2025-02-09 08:39:17.474 [info] message 0 returned. finish reason: [tool_calls]
2025-02-09 08:39:17.475 [info] request done: requestId: [11382f5d-a974-4863-bb91-5d773c275668] model deployment ID: []
2025-02-09 08:43:28.560 [info] message 0 returned. finish reason: [tool_calls]
2025-02-09 08:43:28.561 [info] request done: requestId: [5654ce8a-7d5c-4abe-91f5-85dbb2fc42bb] model deployment ID: []
2025-02-09 08:43:32.863 [info] message 0 returned. finish reason: [tool_calls]
2025-02-09 08:43:32.863 [info] request done: requestId: [5654ce8a-7d5c-4abe-91f5-85dbb2fc42bb] model deployment ID: []
2025-02-09 08:46:11.323 [info] message 0 returned. finish reason: [stop]
2025-02-09 08:46:11.324 [info] request done: requestId: [0ea7a108-6f69-4ea5-a544-94d35222388f] model deployment ID: []
2025-02-09 08:46:11.895 [info] message 0 returned. finish reason: [stop]
2025-02-09 08:46:11.896 [info] request done: requestId: [0f3e33e6-5d3c-4e0e-9fef-3bfefc958890] model deployment ID: []
2025-02-09 08:46:12.315 [info] message 0 returned. finish reason: [stop]
2025-02-09 08:46:12.315 [info] request done: requestId: [da824193-99a3-468f-93d8-1e46b459aef0] model deployment ID: []
2025-02-09 08:46:12.331 [info] message 0 returned. finish reason: [stop]
2025-02-09 08:46:12.331 [info] request done: requestId: [23014a62-a9f5-4c94-9db5-ff4b2fe4d0d1] model deployment ID: []
Description
When using the Agent Mode in Copilot Edit, the terminal hangs indefinitely with the message:
Running command in terminal….
This issue occurs while the agent is attempting to execute terminal commands. The process does not complete, and no further output is provided in the terminal.
Steps to Reproduce
Expected Behavior
The terminal should execute the command and provide the expected output or error message.
Actual Behavior
The terminal hangs with the message:
Running command in terminal…
No further progress is made, and the process does not complete.
The text was updated successfully, but these errors were encountered: