Skip to content

Copilot runs that end without a final message and with zero changes are not diagnosable or continued - #764

Merged
AdamFrisby merged 1 commit into
mainfrom
codeybox/d89b9a48
Nov 9, 2026
Merged

AdamFrisby merged 1 commit into
mainfrom
codeybox/d89b9a48

Conversation

@AdamFrisby

Copy link
Copy Markdown
Owner

Automated via CodeyBox — work item d89b9a4810c84722b96b260693fbeea4

Initiated by CodeyBox operator


Co-Authored-By: CodeyBox noreply@codeybox.invalid
🤖 Generated with CodeyBox

…, distinct failure kind

Work turns now run Copilot with --output-format json (probed via --help,
plaintext fallback with warning), giving the harness the stop/finish reason
plaintext never had: the trailing result event's sessionId/exitCode/
usage.codeChanges plus the concluding assistant.message. The runner owns
session resume (copilot --resume <uuid>, UUID-validated at the argv sink),
quota-gated crash recovery, and a bounded in-session continuation after a
clean-exit turn ends with no final message and no edits
(CodeyBox:Copilot:NoFinalResponseMaxContinuations, default 2, hot-
reloadable). A spent bound stamps EndedWithoutFinalResponse, which the
pipeline classifies as the distinct ended-without-final-response failure
kind instead of quota, transient, or 'produced no changes'.

Verified live against copilot 1.0.106 with a fake chat-completions
endpoint, including --resume with -p in JSON mode.

CodeyBox-Prompt-Revision: 1
Co-Authored-By: CodeyBox <noreply@codeybox.invalid>
@AdamFrisby
AdamFrisby merged commit 95c7b52 into main Nov 9, 2026
6 checks passed
@AdamFrisby
AdamFrisby deleted the codeybox/d89b9a48 branch November 9, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant