Replanning Strategies
Master adaptive replanning strategies to build robust agents that recover gracefully from failures
Your Progress
0 / 5 completedRecovery Approaches
Once you've decided to replan, you face another choice: how extensively should you revise the plan?Different situations call for different levels of replanning. Smart agents choose the minimal replanning strategy that solves the problem, balancing recovery speed against plan optimality.
Interactive: Strategy Explorer
Explore different replanning strategies and their trade-offs
Full Replan
Discard the entire plan and generate a completely new approach
✅ Benefits
- • Optimal new path (not constrained by old plan)
- • Considers all alternatives fresh
- • Can leverage new information
- • No baggage from failed approach
❌ Drawbacks
- • Most time-consuming option
- • Loses progress on completed subtasks
- • May choose same failing approach again
- • Resource intensive (LLM calls, computation)
💡 When to Use
When core assumptions are violated and the entire plan is invalid
Strategy Selection Guide
🔄
Choose Full Replan When:
- • Core assumptions completely broken (e.g., required API removed)
- • Multiple cascading failures make plan unsalvageable
- • New information suggests radically better approach
- • Quality matters more than speed
🎯
Choose Partial Replan When:
- • Failure in middle of execution (early work still valid)
- • Only one subtask/branch failed, rest is fine
- • Want to preserve completed progress
- • Moderate time/quality balance needed
🛡️
Choose Fallback When:
- • Failure mode is common and anticipated
- • Backup plan already exists and tested
- • Speed is critical (immediate recovery needed)
- • Predictability valued over optimality
📉
Choose Degraded Mode When:
- • Partial results better than no results
- • Time is extremely constrained
- • User prefers something vs waiting for replan
- • Reduced functionality is acceptable