Help us improve
Share bugs, ideas, or general feedback.
From dx
Clones the current Claude conversation via bash script and jq to branch off and try alternative approaches. Access cloned session with `claude -r` marked `[CLONED <timestamp>]`.
npx claudepluginhub ykdojo/claude-code-tips --plugin dxHow 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.
Clones the later half of the current conversation, discarding earlier context to reduce token usage while preserving recent work. Useful for long Claude sessions.
Samples sparse conversation history from Claude projects and Codex sessions to infer current worktree context without loading full transcripts.
Searches Claude Code conversation history by topic or date filters, returning session IDs and project paths for resumption via 'claude --resume'. For queries like 'find conversation about X' or 'what did we do yesterday'.
Share bugs, ideas, or general feedback.
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])