Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

Self-hosted sandbox workers can now mount memory stores

Use it now
Useful4 Signal4
Sandbox Notable not in their notes

Shared memory stores now mount on your own sandbox workers, with tunable sync interval and deletion handling.

memory_sync_intervalmemorySyncIntervalMsMemorySyncIntervalmemory_sync_deletesANTHROPIC_WORK_SECRET
What

Shared 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).

Details
  • 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.
  • read_only is enforced by the worker's own tools, not by filesystem permissions, and memory files are opened with O_NOFOLLOW.
  • A new per-session credential, ANTHROPIC_WORK_SECRET, must be forwarded into sandbox-per-session containers.
  • The ant CLI worker does not mount stores at all.
  • memory_store is the only resource type self-hosted environments accept.
Evidence

the worker opens memory files with O_NOFOLLOW``

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.236 →