/resume should list all sessions, not only sessions from the current workspace

Summary

The /resume command only lists sessions associated with the current workspace instead of displaying all available Command Code sessions.

This makes it impossible to resume a session after a workspace has been renamed or moved, even though the session still exists. In comparison, Antigravity CLI allows resuming any session regardless of the current working directory.

I believe /resume should either:

• List all available sessions by default (similar to Antigravity CLI), or
• Provide a toggle/filter to switch between all sessions and sessions from the current workspace.

Expected Behavior

The /resume command should display all Command Code sessions regardless of the current workspace.

If workspace-based filtering is desired, it should be optional through a toggle or filter instead of being the default behavior.

Actual Behavior

The /resume command only displays sessions associated with the current workspace. Sessions created in other workspaces are hidden and cannot be resumed unless Command Code is launched from the original workspace.

Steps to reproduce the issue

1. Create a new workspace.
2. Launch Command Code in that workspace and start a chat session.
3. Rename the workspace folder or move it to a different location.
4. Launch Command Code from the new workspace location.
5. Run /resume.

Result: The previously created session is no longer listed, even though it still exists.

Command Code Version

0.44.1

Operating System

Windows

Terminal/IDE

Unknown

Shell

cmd.exe

Additional context

No response