{"version":"2.1.301","anchor":"mcp-task-metadata-path-resolved-differently","canonical_anchor":"mcp-task-metadata-path-resolved-differently","heading":"MCP task details are saved to a differently chosen folder","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/mcp-task-metadata-path-resolved-differently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### MCP task details are saved to a differently chosen folder\n\nClaude Code now picks the folder for saved MCP task details in a different way, and skips saving when it cannot settle on one\n\n**Unclear.** Where MCP task details are now saved, and in which situations saving is skipped, is not clear.\n\n**What**\n\nClaude Code saves some details about tasks run by MCP servers, the add-ons that give Claude extra tools. The folder it saves them to is now worked out differently, and the save is skipped when no folder can be found. Before, the save was skipped based on which mode Claude Code was running in.\n\n**Why**\n\nThis could change where MCP task details end up on disk.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}