{"version":"2.1.223","anchor":"cloud-sessions-started-with-a-title-rename-themselves-instea","canonical_anchor":"cloud-sessions-started-with-a-title-rename-themselves-instea","heading":"Cloud sessions started with a title rename themselves instead of auto-titling","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/cloud-sessions-started-with-a-title-rename-themselves-instea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Cloud sessions started with a title rename themselves instead of auto-titling\n\nCloud sessions you start with --name keep that name instead of being overwritten by a generated title.\n\n**What**\n\nA cloud session created with an explicit name keeps that name rather than having a generated title overwrite it.\n\n**Details**\n\n- Session bootstrap emits a `rename_session` control request when a title is supplied, with a request id assembled as rename-session-<uuid>.\n- The remote attach path now passes both `title` and `hasExplicitTitle` in the teleport\/cloud session options.\n- The automatic title-generation callback bails out when `hasExplicitTitle` is set, alongside the existing checks for initialPromptUuid, viewer-only sessions and attach-to-existing sessions.\n- The CLI `--name` value is now trimmed and sanitized before use rather than only `.trim()`ed.\n\n**Evidence**\n\n`hasExplicitTitle`, `rename_session`\n\n- Area: Cloud Sessions\n- Names: `--name`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}