{"version":"2.1.248","anchor":"remote-sessions-track-retired-permission-requests","canonical_anchor":"remote-sessions-track-retired-permission-requests","heading":"Remote sessions track retired permission requests","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-sessions-track-retired-permission-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote sessions track retired permission requests\n\nPermission answers now carry a tool-use id too, so the server can match them two ways.\n\n**What**\n\nThe remote session manager now keeps a set of permission requests it has retired, and permission answers carry the tool-use id as well as the request id, giving the server two ways to match an answer to what asked for it.\n\n**Details**\n\n- A model-resolution call site now passes a threaded-request flag, hard-coded to false in this build.\n\n**Evidence**\n\n`retiredPermissionRequestIds`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}