{"version":"2.1.283","anchor":"cowork-memory-context-anchored-memory-attachments-get-their","canonical_anchor":"cowork-memory-context-anchored-memory-attachments-get-their","heading":"Cowork memory context is now placed before its anchor instead of shown directly","tier":"internal","area":"Cowork","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/cowork-memory-context-anchored-memory-attachments-get-their","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cowork memory context is now placed before its anchor instead of shown directly\n\nIn Cowork, memory context entries with an anchor are no longer shown directly; the latest unanchored version's content is inserted before the anchor\n\n**Unclear.** What triggers this code and whether it is switched on anywhere is not stated.\n\n**What**\n\nIn Cowork sessions, Claude Code can attach memory context to the conversation. Two things change in how it handles these attachments:\n\n- An attachment that carries an anchor no longer produces anything by itself. Before, every such attachment was shown.\n\n- For each anchored attachment not already preceded by a matching unanchored one, Claude Code finds the latest unanchored version, looks up its content, and inserts that content before the anchor.\n\n**Why**\n\nThis changes what memory context the model sees in Cowork sessions.\n\n- Area: Cowork\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}