In headless text runs, an incomplete ending no longer swallows the last full answer.
What's wrong with this entry?
In -p runs that print plain text, a run that ends incomplete no longer discards the last complete assistant message.
- Applies when the output format is neither
jsonnorstream-json; the last and prior top-level assistant texts are tracked. - If the final result is a success-but-error whose text ends with "The response above may be incomplete." and equals the last assistant text, the prior assistant text is printed above the result.
- Compact boundaries and superseded messages reset the tracker.
The response above may be incomplete.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Non-interactive runs retry a response that was cut off mid-stream
Both mention headless mode
-
v2.1.246
Headless idle detection now waits for background tasks and undelivered notifications
Both mention headless mode
-
v2.1.246
Headless runs no longer report themselves busy while blocked on a prompt
Both mention headless mode