{"version":"2.1.284","anchor":"remote-session-event-post-reports-too-large-separately","canonical_anchor":"remote-session-event-post-reports-too-large-separately","heading":"Remote sessions report too-large events separately","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/remote-session-event-post-reports-too-large-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Remote sessions report too-large events separately\n\nWhen a remote session fails to send an event because it is too large, that failure is now reported as its own case\n\n**Unclear.** Whether Claude Code does anything different when an event is too large is not settled.\n\n**What**\n\nIn a remote session, Claude Code sends session activity to the server as events. When an event is rejected for being too large, the failure is now marked as too large. Before, it was counted as a general error.\n\n**Why**\n\nThis mainly affects the usage data Claude Code reports. The new too-large marker could also let Claude Code respond to oversized events differently.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}