conversation-fork

Forking a conversation allows you to safely test alternative approaches without losing your original progress. It captures the current context using either a light stash-based or heavy worktree-based fork for auditable experimentation.

A git worktree fork is best for heavy experimentation requiring isolated directory management, while a git stash fork provides a lighter approach for quickly testing alternative design options without leaving your current working directory.

Conversation forking provides auditable planning and resume instructions for future merges. It documents your progress during the fork creation, ensuring decision tracking is maintained throughout your AI-assisted workflow.

Forking the current conversation is the best way to explore multiple refactoring options safely. It applies to interactive sessions and supports structured fork creation to test design alternatives without risking your established progress.

Git is required for both light and heavy conversation forks. The light mode uses git stash while the heavy mode uses git worktree, meaning a git environment is necessary to manage the isolated branches and documentation.