{"version":"2.1.280","anchor":"memory-paused-remedy-mapping-added","canonical_anchor":"memory-paused-remedy-mapping-added","heading":"Memory-paused remedy mapping added","tier":"use","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/memory-paused-remedy-mapping-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Memory-paused remedy mapping added\n\nClaude Code now maps a paused-memory state to a specific 'memory_paused' remedy internally\n\n**Unclear.** It is unclear what user-visible effect the 'memory_paused' remedy produces.\n\n**What**\n\nA new internal helper function now recognizes when the reason for a memory-related issue is `'paused'`, and maps it to a remedy labeled `memory_paused`. This ties to the `\/pause-memory` command, which is used to pause Claude Code's memory feature.\n\n**Why**\n\nThis is internal plumbing that lets Claude Code respond appropriately when memory has been paused, rather than treating it as a generic error. It should make behavior around paused memory more consistent, though the finding does not describe exactly what the remedy causes to happen on screen.\n\n- Area: Memory\n- Names: `\/pause-memory`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}