Stats
Actions
Tags
From dx
Clones current Claude Code conversation via bash script to branch and experiment with alternatives. Locate cloned session with claude -r marked [CLONED timestamp].
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 ykdojo/claude-code-tips --plugin dxClones later half of current Claude conversation via bash script to cut token usage, preserving recent work. Preview first, then access new session via claude -r as [HALF-CLONE timestamp].
Sparsely samples Claude and Codex conversation histories to infer worktree focus and restore session context without loading full transcripts.
Manages Claude Code sessions using /rename, /resume, and CLI commands for naming, checkpointing, and resuming workflows in debugging, feature development, PR reviews, and investigations.