{"version":"2.1.221","anchor":"renaming-a-session-propagates-the-new-name","canonical_anchor":"renaming-a-session-propagates-the-new-name","heading":"Renaming a session propagates the new name","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/renaming-a-session-propagates-the-new-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Renaming a session propagates the new name\n\nRenaming a session now cleans up the title and pushes the new name everywhere, not just locally.\n\n**What**\n\nA rename through remote control now normalizes the title the same way as elsewhere and pushes the name onward instead of only writing it locally.\n\n**Details**\n\n- The title goes through the shared title normalizer rather than a bare trim.\n- Unless the session is in the excluded mode, an async name propagation is queued with source \"user\".\n- Propagation failures are logged and do not block the rename.\n- Transcript append behaviour is unchanged.\n\n**Evidence**\n\n`onRenameSession: name propagation failed`\n\n- Area: Sessions\n- Names: `\/rename`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}