zad111ak-ai Adaptive Loops
Self-healing and self-learning system for AI agents. Automatically recovers from errors and remembers what works.
Philosophy
"The best agent is the one that learns from its mistakes without being told."
Two Types of Loops
1. Self-Healing Loop
When a tool fails:
- Detect error type (timeout, auth, rate limit, etc.)
- Apply appropriate adapter (retry, rotate, proxy, etc.)
- Retry with fix
- Record result for future reference
2. Self-Learning Loop
After each task:
- Record outcome (success/failure)
- Note what worked/didn't work
- Update trust scores for approaches
- Apply successful patterns to future tasks
Usage
Pre-flight Check (before action)
# Check for known antipatterns
fact_store(action="reason", entities=["task_type", "past_error"])
# Check for known fixes
ls ~/.hermes/logs/adaptive/
Post-action Capture (after result)
# Record success
cd ~/.hermes/learning_loop
python3 learning.py record coding "fixed proxy issue" true "groq/llama-3.1-8b-instant" "groq"
# Record failure
python3 learning.py record system_admin "config edit failed" false "auto/best-chat" "omniroute"
Error-driven Adaptation
# Automatic error handling
core.handle_error(tool="browser", error_type="timeout", msg="Connection reset", context={})
Adaptation Strategies
| Error Type | Strategy | Example |
|---|---|---|
| Timeout | Retry with backoff | sleep 5 && retry |
| Auth failure | Rotate credentials | Use different API key |
| Rate limit | Wait + retry | sleep 60 && retry |
| DPI block | Switch proxy | Hysteria2 → Tor |
| Model failure | Fallback model | auto/best-chat → groq |
File Structure
~/.hermes/logs/adaptive/
├── browser_errors.jsonl
├── terminal_errors.jsonl
├── web_errors.jsonl
└── ...
What NOT to Ask Dima
- "Can I record a fact?" → Just record it
- "Can I try an alternative?" → Just try it
- "Can I run handle_error?" → Just run it
What TO Ask Dima
- Delete files/services
- Change systemd
- Install new software (pip install)
- Modify proxy/OmniRoute config