{"version":"2.1.292","anchor":"container-restart-reminder-can-name-a-reason","canonical_anchor":"container-restart-reminder-can-name-a-reason","heading":"After a container restart, Claude can be told the reason","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/container-restart-reminder-can-name-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### After a container restart, Claude can be told the reason\n\nThe reminder Claude gets after a container restart can now include a reason for the restart\n\n**What**\n\nSome sessions run inside a container, an isolated environment that can be restarted. After a restart, Claude Code adds a system reminder, a note to Claude inside the conversation, asking it to re-create what it still needs.\n\nThat reminder can now include a reason. With one, it reads \" Re-create anything else if still needed.\" Without one, it still reads \"Re-create them if still needed.\"\n\n**Why**\n\nClaude gets more specific context about what happened after a container restart.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}