Agent terminal gets hung alot - can no longer use Cntrl+C to kick it out

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

recently, the agent was able to read railway logs in terminal ( clicked on “expand” terminal view so i can also view it). but NOW, the agent just sits there after the data has been displayed, and becuase the terminal is NON interactive- i cannot use Cntrl+C like i did before to KICK IT OUT of being “HUNG” so it can proceed with actions based on the data is just read in the terminal

Steps to Reproduce

ask agent to view railway logs, expand the terminal response view into a new terminal instance

Expected Behavior

agent should be able to read the response, and the either automatically can GET OUT of terminal (not get HUNG) and proceed with next steps, OR - i as the user manually Cntrl+C to force it to UN HANG from the terminal so it can take its next steps

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14 (user setup)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

Opus 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

agent terminals MUST be kept INTERACTIVE because sometimes we as the user need to interactive with options the terminal presents (ex. Railway terminal asks “which service do you want to connect to.. etc”

3

Hey, thanks for the report. This might be related to recent changes in the terminal implementation.

Please try:

  1. Open Cursor Settings Ctrl+Shift+J
  2. Go to the Agents tab > Inline Editing & Terminal
  3. Enable “Legacy Terminal Tool”
  4. Press Ctrl+Shift+P > “Terminal: Kill All Terminals”
  5. Fully restart Cursor

Also, please share:

  • Does this happen with all commands or only with Railway logs?
  • Can you share a screenshot of the stuck terminal?
  • The Request ID from chat (Chat context menu > Copy Request ID)

Let me know if this helped.