Summary
The paper proposes SwiftSage that predicts a high-level plan by Swift and prompts LLMs to conduct each high-level subgoal by Sage.
Swift is trained by imitation learning for action planning as fast intuitive thinking and Sage utilizes LLMs for better generalizable planning and exception handling as deliberate thought processes.
The proposed method achieves strong performances on the ScienceWorld benchmark over the recent state-of-the-art.
Strengths
- The paper is generally written well and easy to follow.
- Utilizing LLMs for exception handling seems reasonable.
- The overall two-staged framework (intuitive planning -> deliberate planning) is intuitive and sounds sensible.
- The proposed method achieves strong performance over prior work by large margins in most cases in the ScienceWorld benchmark.
Weaknesses
- Swift adopts imitation learning to train an encoder-decoder (T5) model but I'm not sure why not just prompting LLMs (see Q1).
- The environment provides if the agent fails at an action, which might not be always available (see Q2).
- SwiftSage utilizes LLMs for exception handling but it is not clear if strategies for exception handling provided by LLMs are always useful and can be conducted by agents (Q3).
- The motivation of each condition of switching to Sage is missing (see Q4).
Questions
- Q1: The Swift module fine-tunes a T5 model with oracle trajectories of training tasks.
But there is some work [14,A] that plans a sequence of actions by providing task-relevant examples to LLMs.
Is there any reason why the authors take imitation learning rather than prompting LLMs?
Although it is fine-tuning and this is quite efficient compared to training from scratch, it does require additional training.
In addition, wouldn't it be that planning with LLMs can generalize better than the imitation-learning models as we can leverage commonsense knowledge of LLMs?
- Q2: It seems that SwiftSage can perfectly recognize when and why it fails based on the feedback from the environment, which might enable Sage to address exceptions effectively.
Can the proposed method address cases where the failure feedbacks are incorrect?
- Q3: I'm not sure the proposed method can ensure that LLMs always provide helpful exception-handling strategies. If LLMs provide some strategies that the agent cannot conduct (e.g., due to the absence of objects), how can the agent address the exception? Note that this is not about the excitability of plans, which is addressed in the "Grounding stage" in Sec. 3.3.
- Q4: In Sec. 3.4, it seems missing the motivation of the conditions to switch to Sage. Why does each condition imply when to switch to Sage? It would solidify the switching conditions to include them.
References\
[A] Liang et al. Code as Policies: Language model programs for embodied control. ICRA, 2023.
Rating
6: Weak Accept: Technically solid, moderate-to-high impact paper, with no major concerns with respect to evaluation, resources, reproducibility, ethical considerations.
Confidence
4: You are confident in your assessment, but not absolutely certain. It is unlikely, but not impossible, that you did not understand some parts of the submission or that you are unfamiliar with some pieces of related work.
Limitations
The authors have adequately addressed the limitations.