{"version":"2.1.229","anchor":"queued-notifications-for-remote-sessions","canonical_anchor":"queued-notifications-for-remote-sessions","heading":"Queued notifications for remote sessions","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/queued-notifications-for-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Queued notifications for remote sessions\n\nRemote sessions accept and validate a new queued notification message instead of ignoring it.\n\n**What**\n\nRemote sessions can now receive a `queued_notification` message, which previously fell through as an unknown message type and was logged and ignored. Payloads are validated and size-capped, and an oversized one is refused without acknowledgement. The feature is only advertised when the `CLAUDE_CODE_REMOTE` environment variable is set and an SDK transport is active.\n\n**Details**\n\n- App state gained a buffer holding pending notifications, the IDs of ones already drained, and a nudge slot.\n- A registry of queued notifications is passed through to tool execution.\n- Telemetry is recorded under `ccr_queued_notifications`.\n- Outside remote mode the message is rejected with a logged reason.\n\n**Evidence**\n\n`[queued-notifications] queued_notification outside remote mode`, `Ignoring unknown message type`\n\n- Area: Remote Control\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}