Thanks for the update. It’s good to hear the Legacy Terminal Tool helps somewhat with showing output and keeping SSH sessions alive.
The issue where the agent doesn’t recognize command output is a known problem, and the team is working on a fix. There’s a detailed thread with discussion and workarounds here: Agent Terminal not working
To help the engineers, could you please share:
- The Request ID from a specific command where the agent gets stuck (chat menu > Copy Request ID)
- Which terminal profile you’re using (PowerShell, CMD, WSL, Git Bash)
- A screenshot or video of the moment when the agent stops recognizing output
- Logs from Help > Toggle Developer Tools > Console (captured while it’s stuck)
About interactivity: the agent terminal is intentionally non-interactive so the agent can run autonomously. That’s a design choice, but the team is working on improvements.