Glossary term
Vision-Language-Action (VLA) Models
What are Vision-Language-Action (VLA) Models?
Vision-Language-Action (VLA) models are AI systems that combine visual perception, natural language understanding, and action generation in a single architecture, so they can observe a digital or physical environment, reason about user instructions, and execute context-aware commands rather than only describing what they see.
In the realm of digital agents, VLAs serve as the foundational intelligence for "computer-use" AI. These models allow agents to interact with graphical user interfaces (GUIs) much the way a human would, by looking at the screen, interpreting the layout of buttons, text fields, and menus, and generating a sequence of keyboard strokes or mouse clicks to accomplish a specific goal. This capability bridges the gap between digital reasoning and task execution, turning static AI assistants into agents capable of navigating web applications, desktop software, and multi-step workflows.
The architecture of a typical VLA model combines a large language model (LLM) backbone with visual encoders built on the transformer architecture, fine-tuned on datasets of paired screen recordings, human instructions, and corresponding action traces. By processing screenshots or continuous video streams alongside textual prompts, the VLA learns to predict the next logical action in a sequence, translating high-level intent into low-level mechanical execution.
The Evolution: LLMs -> VLMs -> VLAs (Text to Perception to Action)
The development of VLA models is the culmination of a rapid evolutionary progression in AI capabilities, transitioning from pure text processing to rich multimodal perception, and finally to grounded action execution.
Large Language Models (LLMs): The Foundation of Reasoning The journey began with text-only Large Language Models (LLMs). These systems excelled at understanding intent, planning, and generating code or structured text. However, they were functionally blind. An LLM could write a Python script to scrape a website or generate the HTML for a user interface, but it could not actually "see" the rendered website or interact with the interface directly. They operated entirely within the symbolic realm of text, reliant on humans or rigid APIs to execute their plans.
Vision-Language Models (VLMs): Adding Perception The next leap was the introduction of multimodal Vision-Language Models (VLMs). By incorporating visual encoders into the language model architecture, AI systems gained the ability to process and reason about images. A VLM could look at a screenshot of a webpage and describe its layout, identify broken CSS, or extract text from an image. This added the element of perception. The AI could now understand the state of a graphical interface, but it still lacked the native ability to act upon that understanding. It could tell you where a button was, but it couldn't click it.
Vision-Language-Action Models (VLAs): Closing the Loop
VLA models close the loop by introducing an action space as a first-class output modality. Instead of merely outputting a description of a screenshot, a VLA outputs executable commands, similar to function calling in text-only LLMs: click(x: 450, y: 300), type('hello world'), or scroll(down). This requires the model to develop spatial awareness and "UI grounding," the ability to map the conceptual understanding of a user interface element (for example, "the submit button") to a specific coordinate or actionable node in the environment. This evolution from text to perception to action marks the transition from passive AI models to active AI agents.
UI Grounding Mechanics: Screen Coordinates vs. DOM Accessibility Tree Parsing
For a VLA to successfully interact with a computer interface, it must accurately ground its actions in the current state of the UI. There are two primary approaches to UI grounding: pixel-based Screen Coordinate mapping and structural DOM/Accessibility Tree parsing. Modern computer-use agents often employ a hybrid of both techniques to ensure robustness across different environments.
Screen Coordinates (Visual Grounding)
In this approach, the VLA relies entirely on visual input. It ingests a screenshot of the interface and predicts raw X/Y coordinates for mouse actions, mimicking how a human "looks" at the screen and decides where to click. It requires no underlying access to the application's code, making it applicable across web browsers, desktop apps, and even remote desktop streams. However, it is sensitive to screen resolution, scaling, and minor visual changes.
DOM & Accessibility Tree Parsing (Structural Grounding)
This approach bypasses pure visual perception and instead reads the underlying structure of the application, such as the HTML Document Object Model (DOM) for web apps or the OS-level Accessibility Tree for desktop apps. The model is fed a structured text representation of the UI elements, allowing it to interact directly with buttons or input fields by their programmatic IDs or semantic labels. This is precise and resilient to visual restyling, but it fails if the underlying tree is poorly constructed, obfuscated, or inaccessible (such as in legacy software or video games).
| Feature | Screen Coordinates (Visual) | DOM / Accessibility Tree (Structural) |
|---|---|---|
| Input Modality | Screenshots / Video streams | Text / JSON / XML trees |
| Universality | High (Works on any visible GUI, including remote desktops) | Low to Medium (Requires access to application code or OS APIs) |
| Precision | Variable (Prone to minor pixel offsets) | Exact (Interacts with specific programmatic nodes) |
| Resilience | Low (Breaks on resolution changes or minor UI redesigns) | High (Unaffected by CSS changes or visual restyling) |
| Speed/Latency | Slower (Requires heavy visual encoding) | Faster (Processes lightweight text structures) |
| Blind Spots | Visually hidden but functionally active elements | Canvas elements, Flash, video games, heavily obfuscated code |
Benchmarking Action Models: OSWorld, WebArena, and VisualWebArena
Evaluating the performance of VLA models requires complex, interactive environments rather than static datasets. Benchmarking an action model involves dropping the agent into a simulated operating system or web environment and tasking it with achieving a specific goal, measuring accuracy, efficiency, and failure recovery.
WebArena WebArena is a pioneering benchmark designed to evaluate autonomous agents on web-based tasks. It features fully functional, self-hosted web applications encompassing e-commerce sites, forums, content management systems, and developer tools. Agents are evaluated on their ability to execute multi-step textual instructions (e.g., "Cancel my most recent order and request a refund") purely by navigating the DOM and interacting with web elements. WebArena primarily tests structural grounding and long-horizon planning in browser environments.
VisualWebArena Building upon WebArena, VisualWebArena introduces tasks that explicitly require visual reasoning. In this benchmark, text-only parsing is insufficient. The agent must process visual information, such as reading text embedded in images, understanding complex data visualizations, or interpreting spatial layouts that are not accurately reflected in the DOM. VisualWebArena is critical for testing the true multimodal capabilities of VLA models in web contexts, ensuring they can fuse visual perception with structural navigation.
OSWorld OSWorld is the most demanding benchmark for computer-use agents, moving beyond the web browser to full operating system control. It provides a multimodal environment of real computer interfaces (Ubuntu, Windows, macOS) spanning 369 tasks across office applications, file management, terminals, and browsers. Agents rely heavily on visual grounding (screen coordinates) since structural access is often limited across diverse desktop applications. Success in OSWorld demonstrates a VLA's ability to operate as a generalized digital worker.
The score trajectory is the clearest measure of how fast this field moved. When OSWorld launched in April 2024, the best model completed 12.24% of tasks against a human baseline of 72.36%. Anthropic reported 61.4% for Claude Sonnet 4.5 in September 2025, and by mid-2026 the top entries on the maintained OSWorld-Verified leaderboard report scores in the 80s, past the human baseline for the first time. WebArena followed a similar arc: the original 2023 paper's best agent scored 14.4% against a 78.2% human baseline, and published agents had passed 60% by 2025. Benchmark saturation at the top does not mean the problem is solved; scores measure task completion in controlled environments, not reliability against the messy, authenticated, anti-bot-protected software of real deployments.
Shipped Products: The Computer-Use Landscape
Every frontier lab now ships a computer-use capability, each with a different architectural bet.
Anthropic released the first frontier computer-use API in October 2024, letting Claude drive a desktop through screenshots and coordinate-based clicks. The capability matured through the Claude 4 series into Claude Code and enterprise agent deployments, with pure visual grounding as the core approach: no DOM access required, so any visible interface works.
OpenAI launched Operator in January 2025 on a dedicated Computer-Using Agent (CUA) model, then folded it into ChatGPT agent in July 2025, which combines browser control with terminal and API tools in a sandboxed virtual machine.
Google previewed Project Mariner in December 2024 and shipped the Gemini 2.5 Computer Use model via API in October 2025, deliberately scoped to browser control, where DOM-aware, web-native actions beat generic screen operation on speed and reliability.
The same architecture runs the robotics side under the original meaning of VLA, a term Google DeepMind's RT-2 paper coined in 2023. Open and commercial robotic VLAs now include OpenVLA (a 7B open-source model, 2024), Physical Intelligence's pi-0 and successors, Google DeepMind's Gemini Robotics (2025), Figure's Helix, and NVIDIA's GR00T line for humanoids. Digital and physical VLAs share the same recipe, a vision-language backbone fine-tuned on paired observation-action trajectories, differing mainly in action space: keyboard and mouse events for one, joint angles and end-effector poses for the other.
Production Safety, Human-in-the-Loop, and Error Recovery for Computer-Use Agents
Deploying VLA-driven computer-use agents in production environments introduces security and operational risks. An agent capable of independently controlling a mouse and keyboard can inadvertently delete critical files, send inappropriate emails, or compromise system security if it hallucinates or misinterprets instructions. Production readiness requires safety protocols such as LLM guardrails and dependable error recovery mechanisms.
Sandboxing and Blast Radius Containment
The foundational rule of deploying action models is containment. Agents should never operate directly on a user's primary machine without explicit, narrow permissions. Production systems isolate agents within secure, ephemeral virtual machines or tightly scoped browser containers. Network access is heavily restricted, and the agent is granted only the minimum necessary credentials (Principle of Least Privilege) required to complete its specific task. This limits the "blast radius" if the agent goes rogue or encounters a catastrophic failure.
Human-in-the-Loop (HITL) and Authorization Gates
For high-stakes actions, autonomous execution must be gated by human oversight. Production frameworks implement human-in-the-loop workflows, pausing the agent's execution before it commits irreversible actions, such as transferring funds, dropping a database table, or sending external communications. The agent prepares the action, presents a summary of its intended steps and a screenshot of the current state, and awaits explicit user authorization before proceeding. This approach balances automation speed with human judgment.
Error Recovery and State Verification
Unlike static text generation, GUI interactions are highly volatile. A website might take too long to load, a pop-up might obscure a button, or an application might crash unexpectedly. VLA models must be engineered with error recovery loops. After executing an action, the agent must observe the new state of the environment and verify that the intended outcome occurred. If the agent clicks "Submit" but the page does not change, it must recognize the failure, reason about the cause (e.g., a missing required field), and attempt a corrective action rather than blindly continuing its planned sequence. This self-correction capability is the defining characteristic of a reliable autonomous agent.
Frequently Asked Questions
Have computer-use agents reached human-level performance? On benchmarks, yes; in practice, not reliably. Top OSWorld-Verified entries passed the 72.36% human baseline in 2026, up from 12.24% for the best model at the benchmark's April 2024 launch. But benchmark tasks run in clean, sandboxed environments. Real deployments face authentication, anti-bot systems, ambiguous instructions, and the cost of a single wrong click, which is why production computer-use agents still ship with human-in-the-loop gates on consequential actions.
Are VLA models only useful for digital tasks, or can they control physical robots? While this article focuses on digital computer-use agents, VLA architecture is equally applicable to physical robotics. In robotic applications, the visual input comes from camera feeds, and the action space consists of joint movements, end-effector coordinates, and torque commands. The underlying principle, mapping multimodal perception to actionable intent, remains the same.
How much latency do VLA models introduce compared to traditional automation? VLA models inherently introduce higher latency than rigid programmatic automation (like Selenium or Playwright) because they must run heavy inference cycles for every step. However, their value lies in adaptability. While a traditional script breaks immediately if a UI button moves five pixels to the left, a VLA agent will visually identify the new location and proceed, trading millisecond-level execution speed for extreme resilience and flexibility.
Can VLA models bypass CAPTCHAs and anti-bot systems? Advanced VLA models, because they process visual information and control a mouse in a human-like manner, can technically solve many visual CAPTCHAs. However, most commercial VLA providers explicitly restrict this behavior in their terms of service. Furthermore, modern anti-bot systems increasingly rely on behavioral heuristics and network fingerprinting rather than simple visual puzzles, making evasion complex even for sophisticated agents.
What is the difference between an RPA bot and a VLA agent? Robotic Process Automation (RPA) bots follow strict, rules-based scripts (e.g., "click coordinate X, then type string Y"). They lack understanding and break when the environment changes. A VLA agent is semantic and goal-oriented. You tell it "book a flight to New York," and it dynamically figures out the steps, navigates the interface, and adapts to unexpected pop-ups or layout changes in real-time.
More terms
Continue exploring the glossary.
Glossary term
What is machine perception?
It's time to build
Collaborate with your team on reliable Generative AI features.
Want expert guidance? Book a 1:1 onboarding session from your dashboard.