/list-agents can hide directories and unnamed sessions, pointing you at /rename.
What's wrong with this entry?
On some connections the agent list now hides working directories, drops your own session line unless a human named it, and appends a note telling you to run /rename on that session's own machine to give it an addressable name.
- The renderer takes a new option, off by default, that turns this withholding on.
- Which connections get it is decided by a per-session check on the calling side that this build does not make legible.
(session names and directories not chosen by a human are withheld on this connection \u2014 /rename a session on its own machine to give it an addressable name here)
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
Agent lists say when cloud sessions could not be fetched
Both mention list agent
-
v2.1.221
Renaming a session propagates the new name
Both mention rename
-
v2.1.232
A session that loses its name to another live session is renamed and told why
Both mention rename