Copilot Chat repeats Continue with no response? Stop and preserve state.

A repeated Continue or retry that returns no usable response is different from a normal slow answer. Stop the cycle and inspect the repository before sending another broad request.

Do this first: Capture the visible response, Copilot and VS Code versions, and any request/error details. Check the diff before retrying so repeated requests do not obscure which edits reached disk.

What the failure looks like.

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.

Why it happens.

Issue #5184 records one Copilot Chat 0.25.2025021401 report on VS Code Insiders 1.98.0. Its body does not establish a root cause, current prevalence, or a confirmed workaround.

Fix it without losing the task.

Stop the repeated Continue/retry cycle after the same no-response result. Save the visible error and timestamp.

Inspect Git status, diff, and recent file changes to establish whether any response was applied.

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.

What the next AI should receive.

Copilot Chat and VS Code versions, exact retry sequence, response/error text, time of failure, files changed across retries, and one small next request with a verification condition.

First safe action

Stop sending Continue while the same no-response result repeats. Record the conversation state and compare files and Git history for any partial output.

Evidence boundary

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.

Diagnostic checkpoint

This page concerns repeated no-response retries, not an Agent waiting for a terminal exit or a disabled Send control; those require separate diagnostics.

How ShardStitch helps.

ShardStitch can preserve disk changes, failed attempts, and the next bounded action for a fresh chat or another tool. It cannot recover an answer that was never written to the project or repair Copilot service state.

Source trail.

Copilot retry-loop report, checked September 24, 2026: Copilot issue #5184 was opened February 15, 2025 for Copilot Chat 0.25.2025021401 on VS Code Insiders 1.98.0. The reporter described repeated “Continue” attempts entering a “Sorry, no response was returned” loop and risking generated code. The issue is closed in the now-archived repository; no cause or workaround is established by its issue body, so verify current versions before treating it as a live defect. Browse the project issue tracker.

FAQ.

Should I keep clicking Continue when Copilot returns no response?

No. Repeating the same action without new evidence can make the session state harder to interpret. Stop, inspect the worktree, and retry only with a bounded request.

Is Copilot issue #5184 proof that current Copilot Chat has this bug?

No. It is a historical report for specific versions in 2025. It does not establish current behavior or a confirmed fix.

Scope note: This is a recovery procedure for repeated no-response retries. The linked issue is a dated user report, not a current service status or vendor-confirmed defect.