{"version":"2.1.300","anchor":"sandboxtenant-path-handling-for-multi-tenant-mode","canonical_anchor":"sandboxtenant-path-handling-for-multi-tenant-mode","heading":"Sandbox protects per-tenant folders in multi-tenant setups","tier":"internal","area":"Sandbox","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/sandboxtenant-path-handling-for-multi-tenant-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Sandbox protects per-tenant folders in multi-tenant setups\n\nIn a multi-tenant mode, the sandbox uses per-tenant folders and blocks writes to .claude and resume files inside them\n\n**Unclear.** What turns on the multi-tenant mode is not known, so readers cannot tell whether it applies to them.\n\n**What**\n\nThe sandbox is a safety boundary that limits which files Claude Code's commands can write to. In a multi-tenant mode, where one machine runs sessions for several separate users, it now works out its paths differently:\n\n- Writable folders are per-tenant folders whose names start with `cc-tenant-`\n\n- Temporary files go to a tenant-specific `TMPDIR`\n\n- Writes to `.claude\/**` and `claude-resume-*` inside tenant folders are blocked\n\nBefore, the sandbox used a fixed set of paths under your home folder's `.claude` directory.\n\n**Why**\n\nThis tightens which files can be changed when several people's sessions share one host. It does not change ordinary single-user use.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}