Hey, thanks for the detailed report. This is a known class of issues with the agent shell on Windows. There are a few overlapping tickets here like bootstrap hang, PowerShell profile not loading, and encoding on non-English locales. We don’t have an exact ETA for a fix yet.
Before we dig deeper, a few questions and steps:
- Version 3.0.12 is not the latest. Newer stable builds include improvements around the agent terminal on Windows. Please update to the latest stable and check if it still happens.
- What are your system locale and code page
chcpin cmd? If it isn’t 65001 or UTF-8 like GBK, CP936, CP866, this might be a separate encoding case that drops stdout. - Quick workaround to test: switch your default terminal profile to
Command Promptcmd.exe and see if the agent behaves the same. If cmd works reliably, that points to the PowerShell profile or PTY layer. - If you’re using
terminal.integrated.automationProfile.windows, please share the full JSON config for that block and fordefaultProfile.windowstoo.
Related threads with the same symptom, they also include workarounds:
- Shell commands in Agent mode are not returning output
- [Windows] Agent terminal tool: no captured output (~0ms, exit 0) — integrated CMD works; Legacy Terminal enabled; PowerShell blocked by policy
Let me know what you see after the update and the cmd profile test, and we can go from there.