Responses can now include mid-conversation model-switch and system blocks without hitting unknown-type handling.
What's wrong with this entry?
Responses can now contain blocks of type fallback (the point where the API switched models) and mid_conv_system. Token accounting, block dispatch and the streaming handler all handle both explicitly, counting them as "other" tokens and returning quietly rather than treating them as unknown. An additional 400-error classifier also now recognises the effort_unsupported upstream error class.
- The existing
output_configtext match for that error class remains alongside the new classifier.
case "mid_conv_system":
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.233
Streamed events are no longer dropped during shutdown
Both mention streaming
-
v2.1.247
The
interruptible_tool_in_progressstream event is goneBoth mention streaming
-
v2.1.248
Streaming deltas can no longer crowd out task lifecycle events
Both mention streaming