Conversation Branching Overview
ZeroTwo uses a tree structure for conversations, allowing you to explore multiple paths from any point without losing previous work. This powerful feature enables experimentation, comparison, and iterative refinement.Understanding Conversation Trees
Conversations aren’t linear - they’re branching trees of possibilities.Tree Structure Visualization
Creating Branches
There are several ways to create new conversation branches.- Edit Messages
- Regenerate Responses
- Continue from Earlier
Hover over a message
Click Edit
Modify and save
New branch created
Navigating Branches
Move between different conversation paths efficiently.Visual Branch Indicators
Branch markers you’ll see:Branch Icon
Active Path Highlight
Response Counter
Breadcrumb Trail
Navigation Methods
- Click to Switch
- History Panel
- Search Branches
Branch Management
Organize and clean up your conversation branches.Viewing Branch Information
For each branch, you can see:- 📊 Number of messages in branch
- 🕐 When branch was created
- 📝 Branch starting point (edited message or regeneration)
- 🎯 Current active branch indicator
Comparing Branches
Enable comparison mode
Select branches
View differences
Choose best approach
Pruning Branches
Keep your conversation organized by removing unsuccessful paths. To delete a branch:- Navigate to the branch you want to remove
- Click the ⋮ More menu in chat header
- Select Delete Branch
- Confirm deletion
Continue Conversations
Resume and extend conversations in powerful ways.Continue from Any Point
You can continue the conversation from any message, creating a new direction:Find starting point
Click or type
Send message
Explore new direction
Long Conversation Management
For complex, multi-session work:- Conversation Summaries
- Export and Continue
- Branch Checkpoints
Advanced Branching Techniques
Parallel Exploration
Explore multiple approaches simultaneously:Create multiple branches
Develop each independently
Compare results
Synthesize or choose
Iterative Refinement
Use branches for progressive improvement:Hypothesis Testing
Test different assumptions with branches:Technical approach testing
Technical approach testing
- Branch 1: “Let’s optimize database queries”
- Branch 2: “Let’s add caching”
- Branch 3: “Let’s use pagination”
Parameter exploration
Parameter exploration
- Branch A: Using collaborative filtering
- Branch B: Using content-based filtering
- Branch C: Hybrid approach
Learning paths
Learning paths
- Branch 1: Deep dive into useState
- Branch 2: Deep dive into useEffect
- Branch 3: Deep dive into useContext
- Branch 4: Custom hooks tutorial
Use Cases and Patterns
Debugging Complex Issues
Initial problem description
Create diagnostic branches
- Branch A: Investigate event handler
- Branch B: Check state management
- Branch C: Review component lifecycle
Follow promising leads
Solve and document
Architecture Decision Making
Learning and Exploration
Pattern: Progressive topic explorationBest Practices
Name your mental branches
Name your mental branches
- “Performance optimization path”
- “Security-focused approach”
- “Beginner-friendly version”
- “Enterprise-scale solution”
Don't fear branching
Don't fear branching
- Create branches to test ideas
- Try unconventional approaches
- Ask “what if” questions
- Explore multiple solutions
- Worry about “wasting” messages
- Fear creating too many branches
- Hesitate to try something new
Use branches for versions
Use branches for versions
Document important branches
Document important branches
- Star the message
- Add a note explaining why this approach won
- Export the branch for documentation
- Reference in future conversations
Clean up regularly
Clean up regularly
- Review all branches
- Delete dead-end explorations
- Keep only promising/reference branches
- Export important solutions before deleting
Keyboard Shortcuts
Speed up branch navigation:Branch Examples
Example 1: Code Review Process
Example 2: Writing and Editing
Example 3: Problem Solving Journey
Troubleshooting
Lost in too many branches
Lost in too many branches
- Open History panel to see full structure
- Use search to find specific content
- Delete unsuccessful branches
- Star your current best solution
- Consider starting a new chat with the best solution copied over
Can't find a previous branch
Can't find a previous branch
- Use Search (Cmd/Ctrl + F) to find content
- Open History panel to view tree structure
- Check Starred messages for important points
- Use Export to search full conversation text
Accidentally deleted important branch
Accidentally deleted important branch
- Export important conversations regularly
- Star critical messages before deleting
- Use deletion carefully
- Keep backups of important solutions

