Move a project folder AND migrate all its Claude Code state in one shot — session store, prompt-up-arrow history, running-session records. Supports both directory-level moves AND session-level cherry-picking (by id, regex on first user prompt, or interactive picker). Use whenever the user wants to rename/move a project directory and keep `claude --resume` working, or wants to move a subset of chats from one project to another. 移动/重命名项目目录并迁移所有 CC 历史，或按 session 粒度把某个话题的对话搬到另一个项目。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Move a project folder AND migrate all its Claude Code state in one shot — session store, prompt-up-arrow history, running-session records. Supports both directory-level moves AND session-level cherry-picking (by id, regex on first user prompt, or interactive picker). Use whenever the user wants to rename/move a project directory and keep `claude --resume` working, or wants to move a subset of chats from one project to another. 移动/重命名项目目录并迁移所有 CC 历史，或按 session 粒度把某个话题的对话搬到另一个项目。
when_to_use
Directory-level — move/rename a project folder AND keep CC history working:
- "把这个项目移到 X" / "把项目从 A 搬到 B" / "rename this folder to X" / "mv this repo to X"
- "本项目之前是在 X" / "这个项目原来在 X" (post-move recovery — use --no-mv or the cc-migrate-session alias)
- "claude --resume 找不到" / "cc --resume 找不到历史" / "恢复旧会话"
Session-level — migrate only SOME chats from FROM to TO (not the whole dir):
- "把 A 里关于 X 话题的 session 搬到 B" / "只搬这几个会话" / "migrate only the chats about ..."
- "A 里的 session 我只想要其中几个" / "split these sessions out into a new project"
- User names a specific session id or describes session content to filter by
NOT for file/function/branch renames — only project root dir moves.
license
MIT
compatibility
claude-code
metadata
{"version":"0.3.0"}
lov-cc-mv
Two modes in one tool:
Directory-level (default) — four things in one shot:
mv FROM TO on disk (fs.renameSync — instant, preserves everything)
Rewrites ~/.claude/projects/<slug>/*.jsonl session store — including every sub-directory slug
Parse sessions[*] — each has sessionId, firstUserPrompt, mtime, sizeBytes, messageCount.
Match the user's intent against firstUserPrompt yourself:
If the topic is unambiguous (e.g. "about command vs skill" + exactly one session's prompt obviously matches) → pick it directly, proceed to Step 4 with --session <id> flags.
If a regex captures it cleanly (e.g. topic = "slash command") → use --grep '<pattern>' instead of passing ids.
If multiple sessions could match and you can't disambiguate from firstUserPrompt alone → show the user the shortlist and ask which ones.
If the user asked for interactive picking explicitly → run with --pick and let the CLI do the UX.
Exclude the current running CC session from the selection — it's the one the user is talking to you from right now, migrating it mid-conversation will break things. (Its sessionId matches the session file that was written to most recently; safer signal: ask the user to confirm if ambiguous.)
Step 4a — Dry-run + json to preview (directory-level)
Total sessions and affected slug count (pairs[*] with sessionCount > 0)
If pairs.length > 1: flag that sub-directories also have CC history
If toDirExistsOnDisk and FROM also exists: warn — CLI will refuse the fs mv
If any pairs[i].toSlugDirExists: warn — destination slug dir will be merged
If totalSessions === 0 AND the user wanted post-move recovery (FROM path doesn't exist): stop, tell them either (a) FROM path is wrong, or (b) CC never ran there.
Step 4b — Dry-run + json to preview (session-level)
The JSON's sessionLevel: true, resolvedSessionIds: [...], and pairs[0].sessionFilter: [...] confirm which sessions will move.
Summarize for the user: "Will migrate N session(s): ". Get confirmation before executing.
Step 5 — Confirm
For directory-level with sub-dirs: ask "Found N sub-dir(s) with CC history. Migrate everything? [Y/n]" — default yes.
For session-level: always summarize the selected sessions (by first-prompt excerpt) and ask "Migrate these N session(s)?" — especially if you resolved them from a regex or topic match, so the user can catch false positives.
Also ask about --delete-source if the user said anything like "move" (vs "copy") — default to keeping source as safety net, only pass --delete-source when the user explicitly wants it.
Step 6 — Execute
Directory-level:
npx -y @lovstudio/cc-mv <FROM> <TO> --yes --json
For post-move recovery (FROM already moved externally):
result.historyRewrites (0 in session-level mode — expected)
result.runningSessionRewrites
result.sourceSessionsDeleted (only non-zero with --delete-source)
fsMvMethod: "rename", "shell-mv", or null (session-level / --no-mv)
restartHint.cd + restartHint.command
Step 7 — Tell user to restart CC
Directory-level:
✓ Moved FROM → TO and migrated N session(s) across M slug dir(s).
✓ Also rewrote prompt history and running-session records.
Restart Claude Code in the new location:
cd <TO>
claude --resume
(The old slug dirs at ~/.claude/projects/<old-slug>* are untouched — delete
them once you've verified --resume works.)
Session-level:
✓ Migrated N session(s) from FROM to TO.
✓ Source sessions {kept as safety net | deleted}.
To resume one of the migrated sessions:
cd <TO>
claude --resume <session-id>
IMPORTANT: The CURRENT Claude Code session cannot "switch" its own cwd mid-session. The user must exit and re-invoke claude from the new directory. State this clearly.
Skip the filesystem mv (only migrate CC state — post-move recovery)
--json
Machine-readable output (use this from the skill)
--projects-dir <dir>
Override CC projects dir (default ~/.claude/projects)
--session <id>
Session-level: migrate only this id (repeatable)
--grep <pattern>
Session-level: migrate sessions whose first user prompt matches the regex (case-insensitive)
--pick
Session-level: interactive numbered picker
--list-sessions
Print session summaries and exit (pair with --json for scripting)
--delete-source
Delete migrated source sessions after copy+rewrite (default keeps them)
Backwards-compatible alias
npx -y @lovstudio/cc-migrate-session <FROM> <TO> — same tool, but defaults to --no-mv (only migrates CC state, doesn't touch the filesystem). Use when the user already moved the folder externally.
Sub-directory Discovery (directory-level only)
CC's slug rule is: replace every non-[A-Za-z0-9] with -. So FROM/sub slugifies to <fromSlug>-<subSlug>.
The CLI lists ~/.claude/projects/ and takes every slug matching slug === fromSlug || slug.startsWith(fromSlug + "-"). That catches FROM and all descendants in one readdir. It then reads each slug's first jsonl to recover the original absolute sub-path (since slug → path isn't reversible), builds the migration pair, and proceeds.
Session-level mode deliberately ignores sub-dir slugs — the user is cherry-picking sessions, not moving the whole project.
Safety
Old slug dirs are never deleted in directory-level mode. Copy-then-rewrite. Old state survives.
Source session files are kept by default in session-level mode. Pass --delete-source explicitly to remove them.
fs mv refuses if TO already exists on disk (avoid overwrite).
Slug-dir merging is default when dest slug dir exists — conflicting jsonls overwritten.
Session-level + --mv is rejected (doesn't make sense — the folder itself isn't moving).
Malformed jsonl lines are passed through unchanged.
Tell the user to verify claude --resume works at TO before rm -rf of old slug dirs.
