From dx
Clones the current Claude Code conversation so the user can branch off and try a different approach. Useful for exploring alternative solutions without losing context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dx:cloneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Clone the current conversation so the user can branch off and try a different approach.
Clone the current conversation so the user can branch off and try a different approach.
Steps:
tail -1 ~/.claude/history.jsonl | jq -r '[.sessionId, .project] | @tsv'find ~/.claude -name "clone-conversation.sh" 2>/dev/null | sort -V | tail -1
<script-path> <session-id> <project-path>
claude -r and look for the one marked [CLONED <timestamp>] (e.g., [CLONED Jan 7 14:30])npx claudepluginhub philquist/claude-code-tipsClones the later half of a Claude Code conversation to reduce token usage while preserving recent work. Used when conversation context grows too large.
Spawns a new Claude Code session in a separate terminal for parallel tasks, optionally sharing context like git branch, task summary, and key files. Use to multitask without losing current progress.
Manages Claude Code sessions with naming, checkpointing, and resume strategies for long-running work or multi-session debugging.