{"version":"2.1.248","anchor":"the-plan-is-fetched-asynchronously-and-filesystem-paths-beca","canonical_anchor":"the-plan-is-fetched-asynchronously-and-filesystem-paths-beca","heading":"The plan is fetched asynchronously, and filesystem paths became conditional","tier":"internal","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-plan-is-fetched-asynchronously-and-filesystem-paths-beca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The plan is fetched asynchronously, and filesystem paths became conditional\n\nPlans are fetched asynchronously, and file paths appear in responses only for certain sessions.\n\n**What**\n\nFetching the current plan over the control channel now goes through the async path using the session's storage handle rather than a synchronous read. Plan and file-read responses now include the filesystem path only for certain sessions: reads add an absolute path when a per-session check holds, and plan responses include a path when it does not. Which sessions that check selects is decided elsewhere in the bundle.\n\n**Evidence**\n\n`getPlanAsync`\n\n- Area: Plan Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}