{"version":"2.1.260","anchor":"session-name-registry-update-failures-are-now-surfaced","canonical_anchor":"session-name-registry-update-failures-are-now-surfaced","heading":"Session-name registry update failures are now surfaced","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/session-name-registry-update-failures-are-now-surfaced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Session-name registry update failures are now surfaced\n\nFailed session-name registry updates are now logged instead of failing silently.\n\nWhen a background session's display name updates locally but the shared session-registry record fails to update, Claude Code now logs a warning instead of failing silently, since other sessions could otherwise keep showing the stale name.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}