{"version":"2.1.299","anchor":"rewind-logs-a-stand-in-served-event","canonical_anchor":"rewind-logs-a-stand-in-served-event","heading":"Rewind now records when it falls back to a stand-in point","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/rewind-logs-a-stand-in-served-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Rewind now records when it falls back to a stand-in point\n\nClaude Code now records a usage metric and a log entry when rewind serves a stand-in instead of the point that was asked for\n\n**What**\n\nRewind is the feature that takes a conversation back to an earlier point. When rewind serves a stand-in instead of the original point, Claude Code now records this. It sends a usage metric, which is a count Claude Code reports about how a feature is used, and it also writes a log entry.\n\n**Why**\n\nRewind can serve a stand-in when it cannot use the requested point directly, and these records now make it possible to count how often that happens. They do not change what rewind does.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}