Recovery System
The Recovery System is the final piece of OmniIDE's self-healing architecture. When the Verification Engine detects a failure, the Recovery System generates corrective actions and re-executes.
Recovery Pipeline
- Error Context Assembly — Collects the error message, stack trace, related source files, and workspace state
- LLM Analysis — Sends the error context to Gemini or Ollama for root cause analysis
- Fix Generation — The LLM produces a structured fix: code changes, commands, or configuration updates
- Fix Application — The fix is applied to the workspace
- Re-execution — The original command is re-run to verify the fix worked
Retry Behavior
The recovery system will attempt up to omni.agent.maxRetries (default: 3) healing iterations. If the issue persists after all retries, the agent reports the failure and asks for human guidance.
Success rate: In testing, the self-healing recovery resolves 80%+ of common development errors (missing dependencies, syntax errors, import issues) on the first attempt.
Related
- Verification Engine — Error detection
- Self-Healing Terminal — The user-facing healing experience
- Agentic Loop — The execution cycle