{"version":"2.1.246","anchor":"changing-directory-now-re-evaluates-plugins-and-mcp-servers","canonical_anchor":"changing-directory-now-re-evaluates-plugins-and-mcp-servers","heading":"Changing directory now re-evaluates plugins and MCP servers","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/changing-directory-now-re-evaluates-plugins-and-mcp-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Changing directory now re-evaluates plugins and MCP servers\n\nChanging the session directory now re-reads plugin and MCP config and reconnects servers.\n\n**What**\n\nWhen a client changes the session working directory, plugin and MCP configuration is re-read for the new location. Servers whose config no longer applies are marked stale and their cache cleared, then servers reconnect or disconnect with the reason `set_cwd`.\n\n**Details**\n\n- Plugins are re-applied without installing anything staged.\n- Failure here is non-fatal: it logs `set_cwd: re-homing plugins\/MCP for the new directory failed (continuing)` and the directory change stands.\n- Unguarded; applies to everyone on this build.\n\n**Evidence**\n\n`set_cwd: re-homing plugins\/MCP for the new directory failed (continuing)`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}