Renaming a session now cleans up the title and pushes the new name everywhere, not just locally.
What's wrong with this entry?
A rename through remote control now normalizes the title the same way as elsewhere and pushes the name onward instead of only writing it locally.
- The title goes through the shared title normalizer rather than a bare trim.
- Unless the session is in the excluded mode, an async name propagation is queued with source "user".
- Propagation failures are logged and do not block the rename.
- Transcript append behaviour is unchanged.
onRenameSession: name propagation failed
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.232
A session that loses its name to another live session is renamed and told why
Both mention rename
-
v2.1.232
/rename can hand a name over to another live session
Both mention rename
-
v2.1.248
/list-agents can withhold session names and directories
Both mention rename