Train agents from scratch without human-annotated data via symbiotic competition—curriculum agent proposes progressively harder tasks while executor agent learns to solve them, creating autonomous self-reinforcing loops.
Train agents from scratch without human-annotated data via symbiotic competition—curriculum agent proposes progressively harder tasks while executor agent learns to solve them, creating autonomous self-reinforcing loops.
Train Agents from Zero Data via Symbiotic Curriculum Competition
Most agent training requires human-curated task datasets or expert demonstrations. Agent0 breaks this dependency via symbiotic competition: two agents create a self-reinforcing loop without external data. A Curriculum Agent proposes increasingly difficult tasks; an Executor Agent learns to solve them. As the executor improves, the curriculum agent escalates difficulty, creating an automatic curriculum.
This achieves significant performance gains (18% on math, 24% on reasoning benchmarks) from a base model with zero human-annotated training data—the only input is the problem domain specification.
Core Concept
Training agents typically requires:
Task datasets (curated by humans)
Reward models (trained on human preferences)
Expert demonstrations (for imitation learning)
Agent0 eliminates these by creating two complementary agents:
Curriculum Agent: Proposes novel tasks from the problem space; initially simple, escalates difficulty as executor improves
Executor Agent: Solves proposed tasks; learns from successes and failures
The feedback loop: Executor improves → Curriculum escalates → harder tasks → Executor gets better signal → loops. This creates high-quality curriculum learning without human intervention.
Architecture Overview
Curriculum Agent: LLM that generates tasks conditioned on executor capability level; uses tool-aware task generation
When to Use: Training agents from scratch when task datasets are unavailable; domains where tasks can be procedurally generated or when self-play/curriculum is feasible (math, coding, games).
Curriculum Design:
Start with simple tasks (one-step solutions); escalate gradually
Introduce tools progressively; hard level introduces complex tool combinations
Success thresholds: 80%+ for escalation, <50% for de-escalation
Pitfalls:
Task degeneration: Curriculum may propose trivial or identical tasks; add diversity metrics and deduplication
Executor plateauing: If executor gets stuck, curriculum tasks may be too hard; implement gradual escalation
Tool usage imbalance: Some tools may be ignored; use tool-hint in curriculum to encourage exploration
Evaluation overfitting: Executor may overfit to curriculum's task distribution; use held-out evaluation set
When NOT to Use: Domains with scarce tool sets; problems requiring external knowledge (not learnable from environment); safety-critical applications.
Integration: Compatible with any LLM; works best with function-calling APIs for tool use.