Messages relayed from your other sessions are now tagged as peer sends rather than looking like scheduled triggers.
What's wrong with this entry?
A message delivered to one session from another of your sessions, sent by the model through a coordinator SendMessage, now carries subkind: "peer-send-message" on its origin instead of being indistinguishable from a scheduled trigger. Anything reading origin.subkind should expect this additional value alongside scheduled-trigger.
- These deliveries keep the same prompt authority as task notifications but are now distinguishable on the wire.
- The classifier stamps the new value when an inbound message arrives over the coordinator path, so the receive-side
crossSessionInboundsetting can apply to it.
so the receive-side crossSessionInbound setting can apply to it
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross