claude-code - 💡(How to fix) Fix VS Code extension: Session rename reverts to auto-generated name after navigating away [1 comments, 2 participants]

TL;DR

The issue can likely be resolved by ensuring that the custom session name is properly persisted when the user navigates away from the session.

Guidance

• Verify that the Enter key press event is correctly triggering the save functionality for the custom session name.
• Check if there are any event listeners or handlers that may be interfering with the save operation when the user navigates away from the session.
• Investigate the data storage mechanism used by Claude Code to store session names and ensure that it is correctly updating the custom name.
• Test if the issue persists when using the standard VS Code extension, to determine if the problem is specific to Antigravity or a more general issue.

Example

No specific code example can be provided without more information on the internal implementation of Claude Code.

Notes

The issue may be related to the way Antigravity handles session data or the integration with VS Code. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround to ensure that the custom session name is persisted, such as manually saving the session after renaming, until a more permanent fix can be implemented. This is because the issue appears to be related to the saving mechanism, and a workaround can help mitigate the problem until the underlying cause is addressed.