{"version":"2.1.275","anchor":"mcp-task-result-saving-now-records-cwd-used-for-the-auth-hel","canonical_anchor":"mcp-task-result-saving-now-records-cwd-used-for-the-auth-hel","heading":"MCP task-result saving now records cwd used for the auth-helper subprocess","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/mcp-task-result-saving-now-records-cwd-used-for-the-auth-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### MCP task-result saving now records cwd used for the auth-helper subprocess\n\nMCP auth-helper subprocess now runs with an explicit working directory when one is set\n\n**What**\n\nWhen Claude Code saves the results of an MCP (Model Context Protocol, a way of connecting external tools) task, it runs an internal `proxyAuthHelper` subprocess to handle authentication. That subprocess now runs with an explicit working directory (`cwd`) when one is available, instead of always using the default.\n\n**Why**\n\nSetting the working directory explicitly makes the auth-helper subprocess behave consistently regardless of what directory it happens to be launched from, which matters when Claude Code needs it to resolve paths correctly.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}