{"version":"2.1.315","anchor":"shell-snapshot-and-sandbox-staging-dir","canonical_anchor":"shell-snapshot-and-sandbox-staging-dir","heading":"Sandbox allows writing to a staging folder for MCP tool calls","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/shell-snapshot-and-sandbox-staging-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Sandbox allows writing to a staging folder for MCP tool calls\n\nThe sandbox now lets Claude Code write to a staging folder for MCP tool calls inside the temporary folder, and warns if it is not a plain folder\n\n**What**\n\nThe sandbox is a restricted environment that limits which files and folders commands can change. It now lets a staging folder for mcp_call requests, which call a tool on an MCP server directly, be written to. That folder sits inside the temporary folder. If the path exists but is not a plain folder, Claude Code shows a warning. This is skipped on Windows.\n\n**Why**\n\nIt gives tools that come from plugins, add-on packages that extend Claude Code, a place they are allowed to write inside the sandbox.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}