{"version":"2.1.281","anchor":"remote-control-rename-can-go-through-a-recordrename-host-hoo","canonical_anchor":"remote-control-rename-can-go-through-a-recordrename-host-hoo","heading":"Remote-control rename can go through a recordRename host hook","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-rename-can-go-through-a-recordrename-host-hoo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote-control rename can go through a recordRename host hook\n\nRenaming a session over remote control can now be handed to the host program through a `recordRename` hook\n\n**Unclear.** The finding does not say which host programs provide `recordRename` or what its v5 storage is.\n\n**What**\n\nRemote control lets you drive a Claude Code session from another place. When a rename arrives this way and the program hosting Claude Code provides a `recordRename` function, the rename takes a new path. Claude Code saves a custom-title entry for the session and then passes the new title and the session's ID to `recordRename`. It no longer uses its own local rename path in that case.\n\n**Why**\n\nPrograms that host Claude Code can now handle session renames themselves, so the new name ends up where the host keeps it."}