Cline shows '[Command is running but producing no output]' after the command finished: what works?
Users of Cline 3.17.15 and 3.18.3 in VS Code 1.101.1 on Ubuntu, Arch, and Windows 11 with PowerShell 7 report that Cline keeps showing '[Command is running but producing no output]' after a command has already finished. Some say curl or httpie are never recognized as finished, and commands using a pager such as psql or git log never exit. Is there a fix or workaround?
Originally asked on GitHub: https://github.com/cline/cline/issues/4356
6 answers
Status: still open. The issue was reopened on the tracker. A contributor who reviewed the consolidated terminal issues says the core problems are mostly resolved for an estimated 90-95% of users, and remaining cases are being handled as individual setup problems. The thread does not state a fix for the '[Command is running but producing no output]' symptom.
Workarounds reported in the thread:
- When Cline shows '[Command is running but producing no output]' after the command has finished, copy the terminal output and paste it into the Cline chat window. This unsticks the session. One user on Ubuntu with Cline 3.18.3 and VS Code 1.101.1 reported this, and another user reported it without giving version details.
- A contributor, citing issue #1101, says a simple terminal configuration works better than complex shell integration. The config given is
export TERM=xterm-256color. - For Windows Server 2019, issue #1476 is listed as including workarounds that involve the Windows 'Use Conpty Dll' setting and a Git Bash configuration. The thread does not give the exact settings.
Other notes from the thread:
- A contributor noted that TerminalProcess.ts filters output aggressively, removing commas and non-alphanumeric characters. This was raised in #1072 and #2523. Using the TTY interface directly was suggested.
- The issue body proposes setting PAGER=cat for Cline terminal sessions to avoid pager hangs. This is a proposal, not a confirmed fix.
General advice: before assuming shell integration is broken, check whether the command is waiting on a pager or an interactive prompt.
Did this work for you?What @Giszmo tried on GitHub (Worked)
A user on Ubuntu with VS Code 1.101.1 and Cline 3.18.3 got past the random '[Command is running but producing no output]' hang by pasting the command and its output into the chat window.
Source: https://github.com/cline/cline/issues/4356#issuecomment-3036836784 (opens external site)
Did this work for you?What @jonworek tried on GitHub (Worked)
A user who sees the message about half the time copied the terminal output and pasted it back into Cline to unstick the session.
Source: https://github.com/cline/cline/issues/4356#issuecomment-3070698976 (opens external site)
Did this work for you?What @celestial-vault tried on GitHub (Worked)
A contributor citing issue #1101 suggested the simple config 'export TERM=xterm-256color' instead of complex shell integration.
Source: https://github.com/cline/cline/issues/4356#issuecomment-2994445662 (opens external site)
Did this work for you?What @celestial-vault tried on GitHub (Outcome unclear)
A contributor added issue #1476 for Windows Server 2019 shell integration failures, noting its community workarounds involve the Windows 'Use Conpty Dll' setting and a Git Bash configuration. The thread gives no exact settings.
Source: https://github.com/cline/cline/issues/4356#issuecomment-2994958044 (opens external site)
Did this work for you?What @dmiric tried on GitHub (Outcome unclear)
A user on Windows 11 with Cline 3.17.15 and PowerShell 7 reported that output reading was hit or miss and that curl or httpie requests were never recognized as finished. No fix was given.
Source: https://github.com/cline/cline/issues/4356#issuecomment-3007660890 (opens external site)
Did this work for you?