Remote session forwarding no longer closes a session by sending an HTTP DELETE. Instead, forwarding outcomes are now classified directly: sent, unchanged, and conflict_resolved map to success, while outcomes like raced, lane_full, unauthorized, deadline, failed, and aborted map to failure. This is part of a reworked remote command-forwarding/session-sync path.
Session-forwarding outcome now classified rather than deleted via HTTP
Remote session forwarding now classifies outcomes directly instead of using an HTTP DELETE.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.260,
Internal ChangesSection of the release