Renaming sessions in the fleet view now always uses the job's state file

The fleet view lists the sessions Claude Code is running or watching. Before, renaming an adopted peer session sent the new name straight to that session over a local socket. An adopted peer session is another running Claude Code session that the fleet view has taken under its watch, and a local socket is a private connection between programs on the same machine. If that session did not answer, you saw a message saying it was not responding.

That path is gone. Every rename now goes through the job's state file, the file on disk where Claude Code keeps a job's details. If the rename fails, the message reads "Couldn't rename - the job may have been removed or its state file is unwritable."