{"version":"2.1.232","anchor":"background-session-names-can-be-marked-as-chosen-to-avoid-a-","canonical_anchor":"background-session-names-can-be-marked-as-chosen-to-avoid-a-","heading":"Background session names can be marked as chosen to avoid a collision","tier":"use","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/background-session-names-can-be-marked-as-chosen-to-avoid-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Background session names can be marked as chosen to avoid a collision\n\nBackground session names auto-changed to dodge collisions now survive respawn like ones you chose.\n\n**What**\n\nA background session's name now records a third origin, `collision`, alongside user-chosen and derived. Names given for this reason are treated like user-chosen ones when a session respawns, so the `--name`\/`-n` flag is preserved rather than dropped, and the session list displays them differently.\n\n**Evidence**\n\n`nameSource === \"collision\"`\n\n- Area: Background Agents\n- Names: `--name`, `-n`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}