{"version":"2.1.323","anchor":"rewound-conversations-get-their-own-stop-reason","canonical_anchor":"rewound-conversations-get-their-own-stop-reason","heading":"Rewinding a conversation now has its own stop reason","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rewound-conversations-get-their-own-stop-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Rewinding a conversation now has its own stop reason\n\nClaude Code now reports \"conversation_rewound\" as the reason work stops when the conversation has been rewound\n\n**What**\n\nRewinding a conversation means taking it back to an earlier point. When that has happened, Claude Code now reports a separate reason for stopping, `conversation_rewound`. This check runs before the check for Claude Code shutting down.\n\n**Why**\n\nClaude Code can now tell that work ended because of a rewind rather than treating it like any other stop.\n\n- Area: Sessions\n- Names: `conversation_rewound`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}