Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Cowork memory may be kept for spawned loops instead of withdrawn

When there is no memory to serve a spawned loop, Cowork may now keep the existing memory context instead of withdrawing it

Under the hood Internal Changes
JSON All of v2.1.319
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
CoworkArea: what it touches
Internal ChangesKind: in v2.1.319,
Internal ChangesSection of the release

Unclear What a user sees differently in a spawned loop is not clear.

What

When a spawned loop has no memory to be given, Claude Code no longer simply sends a notice that the memory has been withdrawn. A spawned loop is a session started from another session. Claude Code may now keep the current version of the memory context in place.

Why

This changes when memory is taken away from spawned sessions.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat a user sees differently in a spawned loop is not clear.

See this entry in the whole of v2.1.319 →

Feedback