Use it now
Useful2 Signal2
Background session names auto-changed to dodge collisions now survive respawn like ones you chose.
What's wrong with this entry?
Anonymous. No account, no email.
--name-n
What
A 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.
Evidence
nameSource === "collision"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background agent failures are labelled with a clearable reason
Both mention background agent
-
v2.1.239
Workers can register as parked instead of idle
Both mention background agent
-
v2.1.239
Background agents screen rebuilt from one large component into several
Both mention background agent