{"version":"2.1.259","anchor":"parked-permission-fallback-can-now-serve-adopted-responses-i","canonical_anchor":"parked-permission-fallback-can-now-serve-adopted-responses-i","heading":"Parked-permission fallback can now serve adopted responses instead of always re-asking","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/parked-permission-fallback-can-now-serve-adopted-responses-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Parked-permission fallback can now serve adopted responses instead of always re-asking\n\nA parked permission that can't be resolved now checks for an already-served response before cancelling and re-asking.\n\nWhen a parked tool-use permission can't be resolved from a persisted `control_response`, the code now first checks for served or adopted responses and uses one if found, instead of always canceling and re-asking. The outcome is logged as `fallback_served_adopted` or `fallback_reask`.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}