{"version":"2.1.235","anchor":"cross-session-message-size-now-fails-with-a-specific-action","canonical_anchor":"cross-session-message-size-now-fails-with-a-specific-action","heading":"Cross-session message size now fails with a specific, actionable error","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/cross-session-message-size-now-fails-with-a-specific-action","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Cross-session message size now fails with a specific, actionable error\n\nOversized cross-session messages now fail with a specific error naming the size and the limit\n\nA new error class `message_too_large` is raised when a serialized cross-session message exceeds the line cap. The error message states both the actual character count and the limit, and suggests putting bulk content in a file instead.\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}