{"version":"2.1.242","anchor":"custom-session-titles-can-be-stored-through-the-v5-backend","canonical_anchor":"custom-session-titles-can-be-stored-through-the-v5-backend","heading":"Custom session titles can be stored through the v5 backend","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/custom-session-titles-can-be-stored-through-the-v5-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Custom session titles can be stored through the v5 backend\n\nCustom session titles can be written through the storage backend, falling back to plain files.\n\n**What**\n\nWriting or deleting the small file that holds a session's custom title now tries the storage backend first, when that backend is enabled and a handle was supplied, and falls back to direct filesystem create and remove otherwise. Failures are logged at error level with a message ending in \"via storage\".\n\n**Details**\n\n- The plugin and marketplace loaders use the same try-storage-then-filesystem shape, now threading credentials through catalog fetches, and gained a path for reading a preview catalog.\n\n**Evidence**\n\n`deleteSessionTitleSidecar: `\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}