{"version":"2.1.323","anchor":"mcp-resources-withheld-from-subagentsbackground-sessions-fo","canonical_anchor":"mcp-resources-withheld-from-subagentsbackground-sessions-fo","heading":"Some MCP servers' resources can no longer be read from subagents or background sessions","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-resources-withheld-from-subagentsbackground-sessions-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Some MCP servers' resources can no longer be read from subagents or background sessions\n\nClaude Code now refuses to read resources from certain MCP servers inside a subagent or background session and tells the model to use that server's tools\n\n**Unclear.** Which MCP servers this refusal applies to is not stated.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools and data. The data they offer for reading is called resources. A subagent is a helper that Claude starts to work on part of a task, and a background session is one that runs without a terminal window attached.\n\nFor certain MCP servers, Claude Code now refuses to read their resources from a subagent or a background session. The refusal explains that the server would treat the request as if it came from the main session. The model is told to use that server's tools instead, if it has them. Before this, only the account memory server was held back this way.\n\n**Why**\n\nSome resource reads that used to work inside subagents or background sessions will now be refused. If a subagent seems unable to read a server's data, this may be the reason.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}