Planning and Skill Acquisition

Voyager

Voyager makes agent competence compound by saving successful behaviors as executable code skills and retrieving them for harder tasks.

8Claims
8Evidence

Why It Matters

The paper is the clearest example of agent skill acquisition as standard-library construction: the agent writes executable functions, tests them in the environment, stores successful ones, and later composes them.

Problem

  • Minecraft is open-ended and lacks a fixed reward or single end goal.
  • RL and imitation methods often operate on primitive actions, making systematic exploration and generalization difficult.
  • LLM agents such as ReAct, Reflexion, and AutoGPT can plan, but do not automatically accumulate reusable embodied skills.
  • One-shot code generation often fails because environment constraints, missing resources, syntax errors, and invalid API calls are discovered only after execution.

Key gap: The paper asks how an LLM agent can explore an open-ended world, progressively acquire skills, and reuse those skills in new worlds without gradient updates.

Method

Let GPT-4 propose a reachable exploration task, generate JavaScript control code, execute it in Minecraft, refine the code from environment and interpreter feedback, verify success, then commit the resulting function to a reusable skill library.

  • Start with no handcrafted task sequence beyond the high-level objective of discovering diverse things.
  • Use the automatic curriculum to select tasks that are challenging but reachable from the current state.
  • Retrieve related skills and generate executable code over control primitive APIs.
  • Execute the code and collect Minecraft observations plus interpreter errors.
  • Iterate code generation up to four rounds using feedback and self-verification critique.
  • If verified, add the function to the skill library and ask for the next task; if stuck, return to the curriculum later.
  • Evaluate exploration, tech-tree progress, map coverage, zero-shot task transfer, and ablations.

Claims

C1 · paper-supported

Voyager combines three modules: automatic curriculum, an ever-growing executable skill library, and iterative prompting with environment feedback, execution errors, and self-verification.

Scope: Abstract, Introduction, and Section 2.

  • E-three-modules: Voyager is described as the first LLM-powered embodied lifelong learning agent in Minecraft, with an automatic curriculum, an ever-growing executable skill library, and an iterative prompting mechanism using feedback, errors, and self-verification.

C2 · paper-supported

The automatic curriculum proposes bottom-up tasks from the agent's current state and exploration progress rather than using a fixed human-written task sequence.

Scope: Section 2.1.

  • E-curriculum: The curriculum prompt uses directives, current inventory/equipment/biome/time/health/hunger/position, completed and failed tasks, and additional GPT-3.5 self-ask/self-answer context to propose a next task.

C3 · paper-supported

Voyager's skill library stores successful behaviors as executable code indexed by embedded descriptions, then retrieves the top relevant skills for future tasks.

Scope: Section 2.2.

  • E-skill-library: Each skill is executable code for a temporally extended behavior. The library indexes the embedding vector of a generated program description and stores the program itself; retrieval queries the top-5 relevant skills.

C4 · paper-supported

The iterative prompting loop uses executed feedback and errors to refine code, and commits code only after self-verification says the task succeeded.

Scope: Section 2.3.

  • E-iterative-prompting: Each generated program is executed to produce environment feedback and interpreter errors. A GPT-4 self-verifier checks task success and critiques failures. The loop repeats until success or after four rounds, at which point the curriculum can choose another task.

C5 · paper-supported

Voyager outperforms ReAct, Reflexion, AutoGPT, and ablated variants on Minecraft exploration, tech-tree mastery, map traversal, and zero-shot generalization.

Scope: Section 3.3 and arXiv abstract.

  • E-main-results: The paper reports that Voyager obtains 3.3x more unique items, travels 2.3x longer distances, and unlocks key tech-tree milestones up to 15.3x faster than prior SOTA. Section 3.3 reports 63 unique items within 160 prompting iterations and says Voyager is the only method to unlock the diamond level.

C6 · paper-supported

The learned skill library transfers to a new Minecraft world and can even improve AutoGPT when used as a plug-in skill source.

Scope: Section 3.3, Table 2, and project repository.

  • E-zero-shot: For zero-shot generalization, the paper resets inventory and world state, tests unseen tasks, and reports that Voyager consistently solves all tasks while ReAct, Reflexion, and AutoGPT solve none within 50 prompting iterations. AutoGPT improves when given Voyager's skill library.

C7 · paper-supported

Ablations identify automatic curriculum, skill library, self-verification, execution feedback, execution errors, and GPT-4 code generation as load-bearing components.

Scope: Section 3.4.

  • E-ablations: The ablation section reports that replacing the automatic curriculum hurts progress, removing the skill library causes later plateauing, removing self-verification produces the largest feedback-type drop, and GPT-4 substantially outperforms GPT-3.5 for code generation.

C8 · paper-supported

Voyager remains expensive, text-only in the reported system, dependent on GPT-4 code quality, and vulnerable to impossible tasks, invalid code, and failed verification.

Scope: Sections 3.5 and 4.

  • E-limitations: The paper notes GPT-4 cost, lack of visual perception in the reported system, cases where the agent gets stuck, occasional self-verification failures, curriculum hallucinations such as nonexistent copper equipment, and code hallucinations such as invalid fuel or absent API calls.

Agent Infrastructure Takeaways

  • A useful agent memory can be executable: Voyager's skills are code functions, not prose summaries.
  • Skill acquisition is a runtime loop: propose task, retrieve skills, execute code, collect errors, verify, then commit.
  • Curriculum is scheduling. The agent needs a policy for choosing the next task at the edge of its current capability.
  • Execution feedback is the external signal that makes self-improvement concrete; without running code, the model has no reliable way to know whether a skill works.
  • A skill library is a shared asset. The paper shows AutoGPT can benefit from Voyager's library, which suggests skills should be portable across agent controllers.
  • Preconditions matter. Vector retrieval of code snippets is useful, but production skill stores also need typed requirements, effects, tests, and provenance.

Caveats

  • The reported system depends on GPT-4 for code generation and self-verification.
  • The environment uses high-level Mineflayer/MineDojo APIs rather than solving perception or low-level motor control.
  • Baselines had to be adapted from non-embodied NLP agent methods.
  • The strongest metrics are Minecraft-specific and may not transfer to physical robotics or arbitrary software tools.
  • Self-verification can be wrong, and the curriculum or code generator can hallucinate impossible objects or invalid APIs.
  • Cost and latency are material because exploration can require many GPT-4 calls.