{"version":"2.1.281","anchor":"claim-session-now-triggers-the-pluginmcp-reconnect-path","canonical_anchor":"claim-session-now-triggers-the-pluginmcp-reconnect-path","heading":"claim_session now triggers the plugin\/MCP reconnect path","tier":"internal","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claim-session-now-triggers-the-pluginmcp-reconnect-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### claim_session now triggers the plugin\/MCP reconnect path\n\nclaim_session now triggers the same plugin and MCP reload as plugin syncs and working-directory changes\n\n**Unclear.** The finding does not say what claiming a session means or when it happens.\n\n**What**\n\n`claim_session` now triggers the step that reloads plugins and MCP servers. MCP, the Model Context Protocol, is a way of connecting Claude Code to outside tools. Other triggers already on that list:\n\n- `plugins_sync`\n\n- `reload_plugins`\n\n- `set_cwd`\n\n- `tool_register`\n\n**Why**\n\nAfter a session is claimed, its plugins and MCP connections are set up again for their new home, through `rehomePluginsAndMcp`.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}