Voyager

In this catalog it is the Frameworks option when you need to compose multi-step agent loops and tool handoffs. Keep Voyager on the observe/propose side of the loop: useful signals and drafts, with human or policy authority still required before anything irreversible runs.

Voyager’s research shape is an embodied lifelong learner: automatic curriculum, a skill library of executable code, and iterative prompting (Minecraft).

1. Curriculum proposes the next skill/task.
2. Agent attempts via iterative prompting.
3. Successful skills are stored as executable code.
4. Skill library compounds into harder tasks.

Related: smolagents · topics/33-skill-registry · topics/12-central-nervous-system

• Use when: Voyager is an LLM-powered embodied lifelong learning agent (Minecraft) with automatic curriculum, skill library of executable code, and iterative prompting matches the bottleneck and you specifically need to compose multi-step agent loops and tool handoffs.
• Skip when: another pack already covers the need with less ops surface, or Voyager would become a second place people retype truth.
• Prefer instead: compare Smolagents before locking the cell.

• Ops: confirm license, hosting, and release cadence for Voyager (MineDojo/Voyager) before relying on it in a live corridor.
• Integration: bad credentials, scopes, or schema drift produce empty retrievals or runaway tool/model spend without an obvious UI alarm.
• Scope: Frameworks components support agents; they are not the company ledger or the approval authority.