Copilot Agent stuck, retrying or incomplete? Verify the work
If the terminal displays a completed command while Copilot Agent keeps waiting, inspect the actual process and terminal result before sending another instruction.
What the failure looks like.
The terminal appears to finish a command, but the Agent run remains waiting or spinning. Issue #13592 is one historical report of this terminal/agent state mismatch.
Why it happens.
A displayed line of output is not always a process exit signal. The issue records one environment-specific report; it does not establish that PowerShell, line endings, or Copilot generally cause this symptom.
If Copilot is waiting for approval.
A permission or approval deadlock is different from a finished terminal command. Preserve the diff, identify the exact approval prompt, then restart with a smaller command or explicit permission boundary. Related failures: Copilot infinite retry loop and Copilot send button disabled.
Fix it without losing the task.
What the next AI should receive.
VS Code and Copilot versions, terminal profile, exact command and exit status, whether a process remained active, output visible to the Agent, current diff, and next verification.
First safe action
Check for a real exit code or a still-running child process. Save the exact command and terminal surface before stopping or restarting the Agent.
Evidence boundary
Issue #13592 concerns Copilot Chat 0.28.2 and VS Code 1.101.2 and is closed as a duplicate. It documents a reported wait after terminal output, not a current general defect.
Diagnostic checkpoint
This page is for an Agent run still waiting after a terminal command. If the Agent says it is complete but the files or checks are wrong, use the repository-verification section below.
Source trail.
Copilot issue #13592 and the Copilot issue tracker.
FAQ.
Does visible terminal output prove Copilot received the command result?
No. Confirm the process exit and inspect the Agent state separately. The user-visible terminal and agent tool state can diverge.
Should I press Enter in the terminal to wake Copilot?
That was a reporter-observed action in one historical issue, not a verified general workaround. Preserve the current state and first confirm whether the command is still active.
Scope note: This is a terminal-state diagnostic anchored to one historical Copilot report. It is not evidence that completion indicators or all terminal integrations are unreliable.
Copilot repeats Continue or returns no response.
The chat repeatedly retries or returns Sorry, no response was returned after Continue. The cited issue is an archived historical report and does not establish behavior in current versions.
- Stop the repeated Continue/retry cycle after the same no-response result. Save the visible error and timestamp.
- Start a fresh minimal request only after confirming that the prior action ended. Include the exact error and ask for one bounded, verifiable step.
- If the issue recurs, collect version and redacted diagnostics and compare with current official Copilot status/support information.
The issue is closed in an archived repository and does not show that current Copilot Chat has the same retry behavior. Treat the report as historical evidence only.
Copilot says complete, but files or checks are incomplete.
The run is reported as complete, but an expected file, code path, or test result is missing or incorrect when checked locally.
- Translate the request into one or more observable acceptance conditions.
- Inspect Git status and the diff, then confirm the expected files and behavior exist in the worktree.
- Run the narrowest relevant test or check and record its exact output. Do not report untested requirements as complete.
- Ask Copilot for only the missing change, providing the current diff and failed check. Re-run the acceptance check afterward.
A passing test covers only the behavior it exercises; a completion message and a partial diff do not establish full correctness. Keep untested requirements marked as unverified.
Additional symptom sources.
How ShardStitch helps.
ShardStitch can preserve the task goal, changed files, terminal output, and last verification for a fresh session. It cannot relay a missed terminal exit event or determine whether a command is still active.