You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a7fcd16
Browse filesBrowse the repository at this point in the historyBrowse files
fix(orchestration): fork from a response a steer cut off
Active steering writes the steer into the same run as the response it
interrupts, and a fork point was always a whole run. So a response a
steer cut off never got a Fork button, and forking its run would have
carried the steer and the reply to it into the fork.
A fork can now end at one assistant response. `thread.fork` takes a
`turn_item` source point (run plus item). The server checks that the item
is a finished assistant message of that run and records the cut on the
transfer and as `forkedFrom.throughTurnItemId`. The inherited timeline, the
windowed history read, search and the shell item count all stop at that
item.
Provider context follows the cut. Claude forks natively: an assistant
item's native id is the SDK message uuid, which `forkSession` accepts as an
inclusive `upToMessageId`. A new optional `canForkFromItem` capability says
so. Codex `thread/fork` only cuts at turn ends, so it and every provider
without the capability get the portable handoff cut at the item, never the
run end.
Web and mobile show the response meta row and Fork on the last assistant
message before each steer as well as the run's last one. Forks from a
mid-run response send the item point; run-end forks still send the run
point. A reply the user stopped mid-stream (interrupted) can be forked
too, matching the server's existing run status rule.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
"Fork a thread from a stable run or checkpoint using the existing fork command. Omit threadId to fork this thread. The fork inherits the source configuration. Acceptance does not mean a provider turn has completed.",
206
+
"Fork a thread from a stable run, a checkpoint, or one finished assistant response (turn_item, which leaves out the rest of its run such as a steer) using the existing fork command. Omit threadId to fork this thread. The fork inherits the source configuration. Acceptance does not mean a provider turn has completed.",
0 commit comments