Cline UI locks up after running a command with no output - how to recover?
I'm using Cline with AWS Bedrock (Claude 3.5 Sonnet v2) in VS Code. When Cline runs a quiet command like
go testwithout-v, the UI locks up: I can't interrupt it or start a new session, and the only recovery is restarting VS Code. The same thing happens with npm/npx commands likenpm run devand with Python commands. Is there a fix or a reliable workaround?Originally asked on GitHub: https://github.com/cline/cline/issues/694
6 answers
No official fix is mentioned in this thread; the issue is closed as completed, but the behavior is explained: Cline keeps waiting for the command's terminal output and never notices the process has already finished, so the UI appears frozen and can't be interrupted. The workarounds below are what users confirmed in the thread.
Fastest recovery: click into the terminal and press Enter. A contributor (comment 6) confirmed this wakes Cline back up when it's stuck waiting for a command that already finished. Try this before restarting your editor.
Kill the focused terminal. Suggested in comment 2 as a way to get Cline going again. The original reporter had not yet tried it at the time of the thread, so treat it as unconfirmed but worth attempting.
Restart the editor. One user reported that with
npm run dev, completely restarting Cursor was the only way to recover (comment 5). This works but is the most disruptive option.MCP server workaround for long-running commands (comment 11). For a Django dev server, the user created a 'terminal' MCP server that launches the command and reroutes its output to a log file, which is then read with
tail -fin another terminal. Cline can start/stop the process and read the log without waiting on terminal output. The user noted it works only 'somewhat' and was only tested with Django, but it's a viable pattern for commands that produce no output for long periods.Did this work for you?What @sammcj tried on GitHub (Worked)
A contributor found that clicking into the terminal and pressing Enter wakes Cline up when it is stuck waiting for a command that has already finished.
Source: https://github.com/cline/cline/issues/694#issuecomment-2547540301 (opens external site)
Did this work for you?What @schbrns tried on GitHub (Outcome unclear)
A commenter suggested killing the focused terminal to get Cline going again; the reporter said they would try it next time but had not confirmed it at the time of the thread.
Source: https://github.com/cline/cline/issues/694#issuecomment-2462866878 (opens external site)
Did this work for you?What @reinierweerts tried on GitHub (Partly worked)
A user created a 'terminal' MCP server that launches commands (Django dev server) and reroutes output to a log file read with tail -f, letting Cline manage the process without terminal output; only tested with Django and works only 'somewhat'.
Source: https://github.com/cline/cline/issues/694#issuecomment-2558471061 (opens external site)
Did this work for you?What @mgunnin tried on GitHub (Worked)
A user reported that after
npm run devcaused the lockup, the only recovery was completely restarting Cursor.Source: https://github.com/cline/cline/issues/694#issuecomment-2470777496 (opens external site)
Did this work for you?What @dldinternet tried on GitHub (Didn't work)
The reporter ran
go testwithout-v(a quiet test with no stdout output) under Cline control with AWS Bedrock and Claude 3.5 Sonnet v2, which triggered the UI lockup.Source: https://github.com/cline/cline/issues/694 (opens external site)
Did this work for you?