session-migrate

To move a Claude Code session to a different project folder, this Skill copies the conversation history and subagents from a source directory to your current working directory and generates a new unique session identifier. This preserves your active conversation context across project boundaries.

Yes, you can resume a Claude conversation started in a temporary directory inside your main project by migrating the session. The process transfers all session files to the current working directory so you can continue your work in the correct project context.

When migrating a Claude Code session between projects, the Skill preserves conversation history and subagents. It copies the session files from the source project folder and assigns a new unique identifier to maintain continuity in the new directory.

Yes, you can look up a specific Claude session ID by filtering project paths. The Skill supports session ID lookup and filtering based on source project paths to help you identify the exact conversation you want to migrate.

No, session-migrate does not require any external dependencies to transfer Claude sessions. It operates using included scripts to copy session files and generate new identifiers without needing additional packages or libraries.

A migrated Claude Code session gets a new unique identifier to prevent conflicts and maintain distinct session tracking within the new project directory. This ensures the copied conversation history integrates cleanly without overwriting existing sessions.