{"version":"2.1.236","anchor":"self-hosted-sandbox-workers-can-now-mount-memory-stores","canonical_anchor":"self-hosted-sandbox-workers-can-now-mount-memory-stores","heading":"Self-hosted sandbox workers can now mount memory stores","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/self-hosted-sandbox-workers-can-now-mount-memory-stores","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Self-hosted sandbox workers can now mount memory stores\n\nShared memory stores now mount on your own sandbox workers, with tunable sync interval and deletion handling.\n\n**What**\n\nShared memory stores, previously documented as unsupported outside Anthropic-hosted sandboxes, now work on your own infrastructure. The Python, TypeScript, and Go worker downloads each attached store to `\/mnt\/memory\/<store-name>\/` and re-syncs it on an interval, default 15s with a 5s floor, tunable via `memory_sync_interval` \/ `memorySyncIntervalMs` \/ `MemorySyncInterval`. Deletion handling is set by `memory_sync_deletes` (`enabled` default, `log_only`, `disabled`).\n\n**Details**\n\n- It is a periodic copy, not a live mount: writes become visible to other sessions only after a sync, and conflicts resolve in favour of the store.\n- `read_only` is enforced by the worker's own tools, not by filesystem permissions, and memory files are opened with `O_NOFOLLOW`.\n- A new per-session credential, `ANTHROPIC_WORK_SECRET`, must be forwarded into sandbox-per-session containers.\n- The `ant` CLI worker does not mount stores at all.\n- `memory_store` is the only resource type self-hosted environments accept.\n\n**Evidence**\n\n`the worker opens memory files with `O_NOFOLLOW``\n\n- Area: Sandbox\n- Names: `memory_sync_interval`, `memorySyncIntervalMs`, `MemorySyncInterval`, `memory_sync_deletes`, `ANTHROPIC_WORK_SECRET`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}