{"version":"2.1.257","anchor":"new-structured-explanations-for-remote-tool-approval-lifecyc","canonical_anchor":"new-structured-explanations-for-remote-tool-approval-lifecyc","heading":"New structured explanations for remote-tool approval lifecycle","tier":"soon","area":"Remote Tool Serving","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-structured-explanations-for-remote-tool-approval-lifecyc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New structured explanations for remote-tool approval lifecycle\n\nNew prose covers remote-tool approval edge cases, from an unresponsive host to a dozen distinct withdrawal reasons.\n\nA new message table (J) generates the user- and model-facing prose for remote-tool approval edge cases: a host asking before tool use, entering plan mode mid-approval, a host going unresponsive during in-flight check-ins, unverified refusals, and withdrawal reasons including `no_answer`, `host_withdrawn`, `superseded`, `evicted`, `tool_withdrawn`, `host_unbound`, `host_stopped`, `stale_answer`, `record_evicted`, `replaced_by_retry`, and `unrecognized`.\n\n- Area: Remote Tool Serving\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}