Group of 2 Under the hood
Session and transcript hydration now track whether messages came from a remote source, changing how artifact state gets rebuilt
What
- Transcript user/assistant messages can now be tagged
remoteSourced: true, and the function that rebuilds artifact state from history now tracks which tool calls came from a remote source and skips local-only reconciliation for those. - A new check decides whether to rebuild artifact state from local history at all, based on whether a message's origin is
"local"and it isseedEligible. - The call that seeds/reconciles initial transcript state now passes an
origin(defaulting to"local") and aseedEligibleflag, threaded through a newinitialMessagesOriginprop on the session engine constructor.
Why This distinguishes messages that came from a remote source (such as headless or remote sessions) from local ones, so artifact-state reconstruction only reconciles local history instead of double-processing remote-sourced tool calls.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what consumes `initialMessagesOrigin` or `seedEligible`, or what practical effect this has for a user.