6 people reported

All time, since Sep 21, including 4 thumbs-up on GitHub.

Session name lost after restart

“Short version: a session renamed with /rename loses that name on every restart and comes back as <dir>-<nn>, so peers can't reach it by name any more.”

Still hitting it after the fix? Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/1752/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Renamed session reverts to derived name after restart. After a reboot or Reload Window, the session comes back as <dir>-<nn> in ListAgents, so peers can't reach it by name.

Is this your bug?

File my report
Where
ListAgents and SendMessage
Versions
2.1.278 to 2.1.287
Platforms
Windows
How bad
Breaks a normal workflow.

Part of: Custom session names don't stick9 bugs

  1. AI title overwrites session name3 people
  2. Rename not synced to remote4 people
  3. Hook sessionTitle ignored in app2 people
  4. Renamed session titles not shown2 people
  5. Exit message omits session name7 people
  6. Session tab rename reverts4 people
  7. Sidebar group membership and session titles don't sync across devices8 people
  8. Session rename reverts10 people

Original reports2, newest first

  1. VS Code: ListAgents name reverts to an auto-generated name after resuming a renamed session#98981
  2. A renamed session reverts to its derived <dir>-<nn> name after any restart, so ListAgents and SendMessage can no longer reach it#95807

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.