Back to AI News
arxiv

VLA Policies Do Not Know When Not to Act: Unintended Task Execution and Start Suppression

A new arXiv study examines whether vision-language-action policies refrain from acting when instructions are missing, meaningless, infeasible, or refer to the wrong task. Across six checkpoints in LIBERO-Goal simulation, an empty instruction still caused movement in every episode, and five checkpoints often completed a task the instruction had not specified. Three suppression approaches were tested: an instruction prefix failed across all six checkpoints, an action-chunk gate held the robot on non-task inputs in five of six, and fine-tuning prevented task completion on non-task inputs but did not reliably keep the robot still or handle infeasible instructions.

AI Brief

It provides concrete evidence that current VLA policies can start and execute tasks without valid instructions, an important safety issue for embodied AI deployment.

arXiv:2610.41609v1 Announce Type: cross Abstract: A robot should act only on an instruction from a person or on an intent that the robot explicitly represents and generates. Unintended actions taken without such an instruction can cause risk or inconvenience to people and the environment. We examine how recent vision-language-action (VLA) policies respond when the instruction is missing or meaningless. We apply a paired protocol with empty, neutral, nonsense, infeasible, and wrong-task instructions to six model checkpoints in LIBERO-Goal simulation. Holding the initial state fixed and varying only the instruction, we ask three questions: whether the robot starts to move, which task it completes, and what the instruction determines. Even when the instruction was empty, the robot started moving in every episode with all six checkpoints, and with five of them it often completed a task that the instruction had not specified. On two GR00T checkpoints, the instruction determined which task was executed but not whether the robot started moving; the robot moved even on infeasible instructions. We then tested three methods for suppressing the start: prepending "if no task is given do not move" to the instruction; a gate that holds the robot when the first action chunk for the given instruction nearly equals that for an empty instruction; and fine-tuning the policy to hold still on non-task inputs. The prefix stopped the robot in none of the six checkpoints, and the gate held it on non-task inputs in five of the six checkpoints. The fine-tuned policy never completed a task on non-task inputs, but it did not reliably keep the robot still, and it failed to suppress the start on infeasible instructions.
Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!