[BUG] Custom session names are lost after restarting VSCode

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Custom session names are lost after restarting VSCode

Description

When I rename a session in the Claude Code VSCode extension, the custom name sometimes reverts to the auto-generated name after restarting the PC and reopening VSCode.

Steps to reproduce

1. Open VSCode with Claude Code extension
2. Rename a session using the edit (pencil) icon in the session list
3. Close VSCode normally (close window / Alt+F4)
4. Shut down the PC
5. Next day, open VSCode again
6. The renamed session has reverted to its original auto-generated name

Expected behavior

Custom session names should persist across VSCode and PC restarts.

Actual behavior

Some or all renamed sessions lose their custom names and revert to auto-generated ones. This does not happen every time, but frequently enough to be disruptive.

Environment

• OS: Windows 11 Pro
• VSCode Extension (not CLI)

What Should Happen?

Custom session names should persist across VSCode and PC restarts.

Error Messages/Logs

N/A

Steps to Reproduce

1. Open VSCode with Claude Code extension
2. Rename a session using the edit (pencil) icon in the session list
3. Close VSCode normally (close window / Alt+F4)
4. Shut down the PC
5. Next day, open VSCode again
6. The renamed session has reverted to its original auto-generated name

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.72

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_