Feature request: fork/move conversation to a different working directory

Use case

When working on a project, it's common to reorganize files — moving a project folder from one location to another (e.g., from ~/Desktop/presentation-devis/ to ~/Documents/UTQR/Master/Presentation Seminaire 1/).

Currently, the conversation is tied to the working directory where it was started. After moving the project, the only option is to start a fresh session from the new directory, losing all conversation context (instructions given, design decisions, iterative refinements, etc.).

Proposed feature

Allow users to fork or move an existing conversation to a different working directory, preserving the full conversation history and context.

Possible UX:

• /fork /path/to/new/directory — creates a new conversation in the target directory with the current transcript
• /move /path/to/new/directory — moves the current conversation to the new directory
• Or automatically detect when the project has moved and offer to re-associate

Why it matters

• Long conversations accumulate valuable context (design decisions, iterative feedback, debugging history)
• Project reorganization is a normal part of development workflow
• Auto-memory helps but doesn't capture the full nuance of an ongoing conversation
• Starting fresh means re-explaining context, which is frustrating and wastes time

Current workaround

• Start a new claude session in the new directory
• Rely on auto-memory for partial context carryover
• Manually re-explain the project state