Under the hood
No documentation found
Rewind failure reasons are now stable codes instead of free-text messages
What
Rewind (the feature that lets you roll conversation history back to an earlier point) used to report failures as human-readable strings like "commands queued", "target not found", "stale target", or "poll tool_result target". These are now built through a shared helper and expressed as snake_case codes: commands_queued, target_not_found, stale_target, poll_tool_result_target.
Why
Stable codes are easier to match on programmatically (for logging, telemetry, or tooling) than free-text messages that could change wording. This doesn't change what rewind does, just how its failures are labeled internally.
Names in the bundlecommands_queuedtarget_not_foundstale_target