Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.236 ·

Self-hosted sandbox workers can now mount memory stores

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

Use it now Notable No documentation found New Features
JSON All of v2.1.236
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SandboxArea: what it touches
New FeaturesKind: in v2.1.236,
What probably matters to youSection of the release
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.

Read from
Names in the bundlememory_sync_intervalmemorySyncIntervalMsMemorySyncIntervalmemory_sync_deletesANTHROPIC_WORK_SECRET

See this entry in the whole of v2.1.236 →

Feedback