{"version":"2.1.323","anchor":"remote-session-title-update-awaits-in-flight-work","canonical_anchor":"remote-session-title-update-awaits-in-flight-work","heading":"Renaming a remote session no longer races with an earlier rename","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-session-title-update-awaits-in-flight-work","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Renaming a remote session no longer races with an earlier rename\n\nRenaming a remote session now marks the title as pending and cancels any earlier title update still in progress\n\n**What**\n\nWhen you rename a remote session (a Claude Code conversation running on another machine), Claude Code now first tells the host that a new title is pending. It then cancels any earlier title update still in progress before it applies the new one. Before, a title update was sent and not followed up.\n\n**Why**\n\nTwo renames in quick succession should no longer leave the session showing an older title.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}