Cline stuck after a terminal command?

A terminal command can block Cline even when the code work is partly done. Separate interactive prompts, watchers, shell state, and API checkpoints before retrying.

Do this first: do not send another broad task. Capture the terminal command, whether it expects input, Cline's last action, changed files, and the checkpoint state.

Terminal states that look like Cline is thinking.

Interactive prompt

The command is waiting for yes/no, credentials, file overwrite, or a package manager prompt. Rerun with non-interactive flags.

Watcher or server

A dev server, test watcher, or long-running process will not return control. Stop it and use a finite command.

Shell boundary unclear

Cline may not know whether the command completed. Verify the output and changed files outside the chat.

Checkpoint or API request follows

If the terminal finished but Cline remains stuck, move to the API/checkpoint recovery path.

Safe recovery path.

Stop the command if it is waiting forever. Keep the workspace; do not clear the whole task first.

Record the command and output. The next attempt needs the exact blocked command and why it blocked.

Inspect checkpoint and Git state. Restore only if the files are wrong. Otherwise continue from the current diff.

Ask for one non-interactive retry. Specify the command, timeout, expected output, and next verification step.

What ShardStitch adds.

ShardStitch converts the blocked terminal state into a handoff: command, output, diff, checkpoint risk, failed attempts, and one safe next action for Cline or another supported tool.

Specific evidence: command output can arrive before Cline continues.

Cline issue #10537 was opened May 4, 2026 and was still open when checked September 24, 2026. The reporter used Cline VS Code extension 3.82.0 (CLI 2.17.0) with VS Code 1.118.1. A chained terminal command returned output, but Cline stayed on “Thinking...” for more than an hour; the report notes mixed stdout/stderr and chained commands as possible triggers, not a confirmed root cause. The reporter's only described exit was cancel/restart; no maintainer fix is recorded.

For diagnosis, record the exact command and whether it is interactive, long-running, or chained. Run a finite version directly in the terminal, capture its exit code and output, then compare git status and git diff with the agent's last checkpoint. If the command finished but Cline remains blocked, preserve the diff before cancelling; do not rerun a command that may still be active.