The --resume-session-at help now explains it takes a chain-entry id, not an assistant message id.
What's wrong with this entry?
The flag's description now describes the id it takes as a chain-entry UUID rather than an assistant message.
- resumes messages up to and including the chain entry with the given id
- help text points at the kept turn's last entry as the typical value
- still documented as print-mode only, used with
--resume
any chain-entry UUID, typically the kept turn's last entry (use with --resume in print mode)
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.228
A /resume mid-upload no longer sends the wrong transcript
Both mention resume
-
v2.1.232
Resuming with an unrecognisable session id now forks instead of resuming
Both mention resume
-
v2.1.239
Resume hints no longer point at directories that are gone
Both mention resume