Oversized messages between sessions now fail with the actual size, the limit, and advice to use a file.
What's wrong with this entry?
Sending a message between sessions that exceeds the size cap now raises a dedicated message_too_large error naming the actual character count and the limit, and suggesting you put bulk content in a file instead.
- Applies to serialized messages on the cross-session delivery path.
- No gate; always active on that path.
cross-session message exceeds the line cap
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