{"version":"2.1.292","anchor":"control-plane-rewind-conversation-treated-like-turn-handoff","canonical_anchor":"control-plane-rewind-conversation-treated-like-turn-handoff","heading":"Rewind requests are now timestamped, and a prompt autocomplete operation appears","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/control-plane-rewind-conversation-treated-like-turn-handoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Rewind requests are now timestamped, and a prompt autocomplete operation appears\n\nRewind requests now get a creation time like turn handoffs, teammate messages can record what kind of recipient they are for, and a prompt autocomplete operation exists\n\n**Unclear.** What the new prompt autocomplete operation does, and whether anything can use it yet, is not stated.\n\n**What**\n\nPrograms that drive Claude Code from outside can send it control requests, which are instructions such as \"take the conversation back to an earlier point\". This release changes three things on that side:\n\n- `rewind_conversation` requests now get a creation time stamped on them. Before, only turn handoff requests got one.\n\n- Messages sent between teammates can now say what kind of recipient they are for.\n\n- A new prompt autocomplete operation and a matching action exist.\n\n**Why**\n\nThe set of things an outside program or another agent can ask Claude Code to do keeps growing, and rewind requests are now handled the same way as turn handoffs when it comes to recording when they were made.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}