Bug: /rename fails with 'Workspace not found' on resumed sessions

[rameshreddy-adutla]

Description

/rename fails with the error:

✗ Error: Workspace not found: 0bedaedd-a600-4bd7-b639-8b839647ae1e

Steps to Reproduce

1. Start a session (session A)
2. End the session
3. Start a new session (session B)
4. Use /resume to resume session A into session B
5. Try /rename <new-name> or /session rename <new-name>
6. Error: Workspace not found: <session-A-id>

Expected Behaviour

The rename should work on the resumed session.

Environment

• Copilot CLI version: v0.0.421
• OS: macOS (Darwin)
• Session state directory exists on disk: Yes (~/.copilot/session-state/<id>/ is present with events.jsonl and plan.md)

Analysis

It appears that when a session is resumed via /resume, the workspace ID from the original session is carried over but not registered in the internal workspace registry. The session-state directory exists on disk, but the CLI cannot find it when performing rename operations.

Workaround

None found. /session rename also fails with the same error.

[examon]

This has been fixed in v1.0.18. The workspace metadata is now properly recreated when resuming a session, so /rename should work correctly after /resume. If you're still seeing this on v1.0.18 or later, please feel free to reopen.