Thanks for the detailed diagnosis in the posts above, it’s genuinely helpful.
I want to clarify my previous reply: removing terminal.integrated.automationProfile.windows won’t help. Cursor on Windows already ignores this setting and always uses PowerShell for the agent. This is a known limitation.
On the current situation:
psql starts, but output isn’t captured: if Legacy Terminal Tool is already enabled and it doesn’t fully help, try restarting all terminals (Ctrl+Shift+P → Terminal: Kill All Terminals) and then fully restart Cursor. More details and discussion in this long thread: Agent Terminal not working.
SSH “Pseudo-terminal will not be allocated”: try adding -t or -tt to your SSH command to force PTY allocation. Legacy Terminal Tool can also help a bit with SSH sessions.
To move forward, we’ll need:
- The Request ID from the chat where psql or SSH fails (chat menu → Copy Request ID)
- Logs from Help → Toggle Developer Tools → Console at the moment the issue happens
The team is aware of the Windows agent terminal issues. Let me know how it goes after these steps.