{"version":"2.1.286","anchor":"cowork-memory-versions-tracked-with-if-version-and-carried-v","canonical_anchor":"cowork-memory-versions-tracked-with-if-version-and-carried-v","heading":"Cowork memory writes now carry version numbers","tier":"internal","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/cowork-memory-versions-tracked-with-if-version-and-carried-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Cowork memory writes now carry version numbers\n\nClaude Code's tracking of Cowork memory now records the version a memory write expects and keeps each memory path's latest version across turns\n\n**Unclear.** It is unclear what switches this on and what uses the recorded versions.\n\n**What**\n\nIn Cowork, Claude keeps memory it can read and write with a memory tool. Claude Code keeps a record of those memory tool calls, and that record changed in three ways:\n\n- It now notes the `if_version` value given with a write.\n\n- It keeps the last version and a carried-over version for each memory path. Before, it tracked only which paths were read and which were written.\n\n- A new warning is logged when passing these versions along fails.\n\n**Why**\n\nThis lets memory writes be checked against a version from one turn to the next.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}