ModelRefs / OSWorld — AI Glossary

OSWorld — AI Glossary

A benchmark evaluating computer-using agents on real desktop tasks across Ubuntu, macOS, and Windows. GPT-4V at launch: ~13% success; humans: 72%.

Overview

OSWorld (Xie et al. 2024) presents 369 real computer tasks (LibreOffice editing, Chrome navigation, file management, VsCode use) with functional verification. Agents observe screenshots and generate mouse/keyboard actions. GPT-4V at launch: ~13% success; humans: 72%. Defines the frontier for GUI/CUA evaluation.

Reference details

Topicevaluation
Last reviewed2026-06-24

How it works

  1. Tasks are posed inside real applications in a real operating system, not in a simulated or text-only environment.
  2. The agent observes the screen and emits mouse and keyboard actions, so the interface is the same one a person uses.
  3. Completion is verified functionally — by inspecting the resulting file or application state — rather than by comparing a transcript.
  4. That verification is what makes the benchmark hard to game: a plausible-looking action sequence that did not produce the state scores zero.
  5. Tasks span several applications and many steps, so per-step reliability compounds and long tasks dominate the difficulty.

Example: Why functional verification is the hard part

An agent is asked to edit a spreadsheet and save it. A transcript-based check might accept a sequence that looks correct. Functional verification opens the saved file and inspects the cell, so an agent that clicked the right menus but never committed the change scores zero — correctly. Across a multi-step task at 90% per-step reliability, ten steps succeed 0.9¹⁰ ≈ 35% of the time, which is why reported success rates on real-computer benchmarks sit far below per-step competence.

Commonly confused with

Grouped with web-agent benchmarks, and the environment is broader. A web benchmark constrains the agent to a browser, where the DOM provides structured observation. This spans a desktop — file manager, office suite, editor, browser — so observation is largely pixels and actions are raw input, with no accessibility structure to rely on. It is also not a reasoning benchmark: the difficulty is grounded interaction and multi-step reliability, so a model that reasons well can still score poorly for lack of precise control.

When to use it

Reach for it when:

  • Evaluating agents that must operate real applications rather than APIs.
  • Functional verification is needed, so plausible-looking action sequences cannot pass.
  • Explaining why multi-step grounded tasks are harder than their per-step accuracy suggests.

Reach for something else when:

  • The target is browser-only automation, where a web benchmark is closer.
  • Measuring reasoning, which this confounds with interface control.
  • As a proxy for your own environment, which differs in applications and layout.

Primary source

Continue your research

Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to OSWorld — AI Glossary.

Frequently asked questions

What is OSWorld?

A benchmark evaluating computer-using agents on real desktop tasks across Ubuntu, macOS, and Windows.

What concepts are related to OSWorld?

Closely related concepts include computer using agent, gaia, web agent.