{"version":"2.1.235","anchor":"remote-replies-the-client-cannot-decode-are-surfaced-instead","canonical_anchor":"remote-replies-the-client-cannot-decode-are-surfaced-instead","heading":"Remote replies the client cannot decode are surfaced instead of crashing or blanking","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/remote-replies-the-client-cannot-decode-are-surfaced-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Remote replies the client cannot decode are surfaced instead of crashing or blanking\n\nUndecodable remote replies now show a clear message instead of crashing or showing nothing\n\nThe context-usage command and the feedback\/review path now validate the remote reply before using it. If the reply can't be rendered by the current client version, the user sees an explicit message, such as \"Couldn't show context usage: the remote sent a reply this version can't display,\" instead of the client crashing or silently proceeding with malformed data.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}