LLM-based planning agents commit to plans of different lengths before interacting with a partially observable environment. Some aggressively commit to a long plan based on assumptions about unobserved states, while others conservatively plan only over what they have observed. Both behaviors emerge implicitly in pre-trained models, whether the LLM outputs a plan directly or generates a PDDL formulation for a classical solver. Aggressive commitment risks costly failures, while conservative commitment risks excessive LLM calls. This choice pits safety against efficiency, a trade-off that has been neither characterized systematically nor made controllable. We investigate aggressive and conservative LLM planners and formalizers on two partially observable domains, where priors are provided as either explicit statistics or common-sense knowledge. Across three LLMs, both strategies reach similar accuracy. Conservative methods achieve fewer failed attempts (safety) at the cost of more API calls (efficiency). Aggressive methods fail more often but replan efficiently only when priors are informative. Interestingly, analysis shows that LLMs treat the provided priors nearly as facts, which risks failure when priors are unreliable. We also explore hybrid strategies with tunable hyperparameters that adjust the balance between safety and efficiency.
Figures & tables
Figure 1: In partially observable environments, models are required to either only make plans from observations when interacting with the environment (Conservative) or assume missing information and replan based on environment interactions (Aggressive).
Figure 2: Overview of all planning and formalization methodologies. While conservative methods (dark green) plan using only observations and subgoals, aggressive methods (orange) come up with the entire plan by assuming missing information. All approaches are evaluated using a simulator.
Figure 3: Results on Coin Collector and ALFWorld for Aggressive vs. Conservative Planner and Formalizer using Planning Accuracy, Average Number of Failed Attempts, Average Number of API Calls and Average Output Tokens on DeepSeek-Flash ( D ), Gemini-3-Flash ( G ) and Qwen3.8-27B ( Q ). For ALFWorld, Gemini-3-Flash is not included due to budget constraints.
Figure 4: Percentage of the times connected lines in problem files do not appear from observations in the environment, but are given in the statistical priors, for Aggressive Formalizer on Coin Collector.
Figure 5: Tradeoff on all evaluation metrics across all methods on partially observable Coin Collector data. Only Gemini results are shown, for all models see Appendix Figure 8 .
Figure 6: Examples of inputs and plans for Coin Collector and ALFWorld. Note that the images provided are for illustration purposes only and our input is purely textual.
Figure 7: (a) The percentage of plans from planner methods that used a connection in Coin Collector that was not observed in the environment. (b) The percentage of connected facts in formalizer methods that contained a connection that did not appear in the environment.
Figure 8: Tradeoff on all evaluation metrics across Conservative, Aggressive and Hybrid (both fixed and free) Planner and Formalizer on partially observable Coin Collector data. Only results when statistics are provided are shown.
Appendix figures & tables14 assets
Supplementary material from the paper’s appendix.
Appendix
Figure 9: Multiple runs of DeepSeek-Flash on Coin Collector data. Note because Conservative methods were not given statistical priors, results are repeated.
Method
Acc. ↑
Fail. ↓
API ↓
Tok. ↓
Aggr. planner
100
4.0
5.0
178
Cons. planner
100
1.5
4.7
197
Aggr. formalizer
90
6.1
7.5
7,603
Cons. formalizer
100
5.7
18.6
16,149
Appendix
Table 1: Gemini-3-Flash on ALFWorld, 10 problems per method. Aggr. and Cons. denote aggressive and conservative. Acc. is accuracy (%), Fail. the average number of failed attempts per problem, API the average number of API calls, and Tok. the average number of output tokens
Baseline
Att.
Steps
Acc.
1-Att.
Oracle BFS
1.00
4.09
100
100
Frontier BFS
6.09
7.15
100
0
Aggressive BFS
5.99
13.60
100
3
Probability
5.34
62.75
100
53
Appendix
Table 2: Non-LLM baselines on Coin Collector. Att. and Steps are the average number of attempts and actions per problem, Acc. is planning accuracy (%), and 1-Att. is the percentage of problems solved on the first attempt.
Method
Fail.
PDDL
Loc.
Known
Assumed
Rev.
Full observability
DeepSeek-Flash
Aggressive
0.00
0.00
0.00
0.00
–
0.00
Aggressive + priors
0.06
0.01
0.00
0.05
–
0.01
Conservative
0.31
0.00
0.30
0.01
–
0.04
Gemini-3-Flash
Appendix
Table 3: Causes of failed attempts for formalizers on Coin Collector (run 1), averaged per problem. Fail. is the total and equals the sum of PDDL (no solvable PDDL after revisions, or an unparsable action), Loc. (wrong agent location in the problem file), Known (contradicts a given or observed connection), and Assumed (relies on an unobserved connection). Rev. is the average number of PDDL revision calls per problem.
Figure 10: Failed attempts and API calls by shortest start-to-coin path length on Coin Collector without connections, averaged over DeepSeek-Flash, Gemini-3-Flash, and Qwen3.8-27B (run 1). n is the number of problems.
Length 2 ( n=42 )
Length 3 ( n=30 )
Length 4 ( n=13 )
Length 5–6 ( n=15 )
Method
Acc.
Fail.
API
Acc.
Fail.
API
Acc.
Fail.
API
Acc.
Fail.
API
Conservative planner
100
0.02
3.14
100
0.06
4.33
100
0.03
5.82
100
0.07
6.62
Aggressive planner
100
1.93
2.93
98
2.78
3.76
100
4.00
5.00
100
4.24
5.24
+ priors
100
0.83
1.83
100
1.20
2.20
100
3.05
4.05
100
2.87
3.87
Conservative formalizer
91
0.61
3.98
94
0.67
5.26
90
1.08
6.51
89
0.91
6.98
Aggressive formalizer
92
1.94
3.14
94
3.01
4.27
82
4.46
5.69
91
4.40
5.64
Appendix
Table 4: Coin Collector results without connections by shortest path length, averaged over the three models (run 1). Acc. is planning accuracy (%), Fail. the average number of failed attempts, and API the average number of API calls.
Figure 11: Example of Gemini-3-Flash as Aggressive and Conservative Planner. While Conservative Planner is able to solve the problem in one attempt, Aggressive Planner is able to solve the problem in fewer API Calls.
Figure 12: Example of Gemini-3-Flash as Aggressive and Conservative Formalizer. When statistical priors are given under partial observability, the Aggressive Formalizer can leverage these priors and come up with the correct plan with deductive reasoning.
Without statistics
With statistics
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Full observability
Planner
Aggressive
100
1.00
0.00
1.00
35
100
1.00
0.00
1.00
35
Conservative
98
1.00
0.02
1.00
35
–
–
–
–
–
Hybrid (free)
100
1.00
0.00
1.00
35
94
1.00
0.06
1.00
35
Appendix
Table 5: Coin Collector results for DeepSeek-Flash (run 1). Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. Conservative methods are not given statistics (–). All rows use 100 problems.
Without statistics
With statistics
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Full observability
Planner
Aggressive
100
1.00
0.00
1.00
35
98
1.00
0.02
1.00
34
Conservative
100
1.00
0.00
1.00
35
–
–
–
–
–
Hybrid (free)
100
1.00
0.00
1.00
35
99
1.00
0.01
1.00
34
Appendix
Table 6: Coin Collector results for Gemini-3-Flash (run 1). Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. Conservative methods are not given statistics (–). All rows use 100 problems.
Without statistics
With statistics
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Full observability
Planner
Aggressive
100
1.00
0.00
1.00
35
98
1.00
0.02
1.00
34
Conservative
98
1.00
0.02
1.00
35
–
–
–
–
–
Hybrid (free)
97
1.00
0.03
1.00
35
98
1.00
0.02
1.00
35
Appendix
Table 7: Coin Collector results for Qwen3.8-27B (run 1). Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. Conservative methods are not given statistics (–). All rows use 100 problems.
Without statistics
With statistics
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Full observability
Planner
Aggressive
100
1.00
0.00
1.00
35
100
1.00
0.00
1.00
35
Conservative
100
1.00
0.00
1.00
35
–
–
–
–
–
Hybrid (free)
100
1.00
0.00
1.00
35
99
1.00
0.01
1.00
35
Appendix
Table 8: Coin Collector results for DeepSeek-Flash (run 2). Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. Conservative methods are not given statistics (–). All rows use 100 problems.
Without statistics
With statistics
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
Full observability
Planner
Aggressive
100
1.00
0.00
1.00
35
100
1.00
0.00
1.00
35
Conservative
98
1.00
0.02
1.00
35
–
–
–
–
–
Hybrid (free)
100
1.00
0.00
1.00
35
96
1.00
0.04
1.00
35
Appendix
Table 9: Coin Collector results for DeepSeek-Flash (run 3). Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. Conservative methods are not given statistics (–). All rows use 100 problems.
Method
Acc. ↑
Att.
Fail. ↓
API ↓
Tok. ↓
DeepSeek-Flash
Aggressive planner
98
3.81
2.83
3.81
146
Conservative planner
100
2.33
1.33
5.69
159
Aggressive formalizer
75
11.40
10.65
12.34
10,240
Conservative formalizer
63
12.21
11.58
24.41
16,718
Qwen3.8-27B
Appendix
Table 10: ALFWorld results for DeepSeek-Flash and Qwen3.8-27B, 100 problems per method, without statistics. Acc. is planning accuracy (%), Att. the average number of attempts per problem, Fail. the average number of failed attempts per problem (attempts minus accuracy), API the average number of API calls per problem, and Tok. the average number of output tokens per problem. All rows use 100 problems.