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.
Every time you edit a message or regenerate a response, you create a new branch. All branches are preserved, letting you explore different approaches and return to any point in the conversation.
You can continue the conversation from any message, creating a new direction:
1
Find starting point
Scroll to the message where you want to branch
2
Click or type
Click the message, then type a new message in the input
3
Send message
Your new message creates a branch from that point
4
Explore new direction
Continue with a different approach or question
Example use case:
You're 20 messages deep into optimizing an algorithm, but realize you should have explored a completely different approach. Click on message 5 and start a new branch with the alternative approach.
Track what each branch explores:Keep a mental (or written) label for branches:
“Performance optimization path”
“Security-focused approach”
“Beginner-friendly version”
“Enterprise-scale solution”
This helps you remember what you were exploring in each branch.
Don't fear branching
Experiment freely:✅ Do:
Create branches to test ideas
Try unconventional approaches
Ask “what if” questions
Explore multiple solutions
❌ Don’t:
Worry about “wasting” messages
Fear creating too many branches
Hesitate to try something new
You can always delete unsuccessful branches later.
Use branches for versions
Iterate on solutions:Pattern:
v1 (Basic): Working solutionv2 (Refined): With error handlingv3 (Production): With tests and documentationv4 (Optimized): With performance improvements
Each version is a branch, easy to compare and reference.
Document important branches
Preserve key decisions:When you find a great solution:
Star the message
Add a note explaining why this approach won
Export the branch for documentation
Reference in future conversations
Copy the full branch into a new conversation titled “Final Solution - [Topic]”
Start: [Upload code file] "Review this code"Main branch: General review with suggestionsBranch A (from message 3): "Focus on security vulnerabilities" └─ Detailed security analysis └─ "Show how to fix the SQL injection risk" └─ Fixed code with explanationBranch B (from message 3): "Focus on performance optimization" └─ Performance analysis └─ "Show before/after benchmarks" └─ Optimized code with metricsResult: Two specialized reviews, choose or combine insights.
Start: "Write a blog post about React hooks"Branch 1: Technical deep-dive version └─ For experienced developersBranch 2: Beginner-friendly version └─ For React newcomersBranch 3: Tutorial format └─ Step-by-step with code examplesEdit Branch 2 further: └─ Branch 2.1: Add more examples └─ Branch 2.2: Simplify explanations └─ Branch 2.3: Add diagramsCompare all, then choose Branch 2.2 as final.