The Agentic Post
Breaking
Gemini’s Multimodal Features, Explained  Â·  ChatGPT Custom GPTs, Explained  Â·  What Is Constitutional AI? Explained  Â·  AI Capex Explained for Investors  Â·  AI Startup Valuations: How They Are Set  Â·  How to Reskill for an AI Job Market  ·  
Home/AI Agents/Computer-Use Agents
A History of Computer-Use AI Agents

A History of Computer-Use AI Agents

Computer-Use Agents

A look at how computer-use AI agents evolved from scripted automation to general vision-based agents, and what recent benchmark data reveals about real progress.

Agents that operate a computer the way a person does went from research curiosity to a genuinely tracked benchmark category remarkably fast, and the pace of that progress is part of the story.

Before general-purpose computer-use agents, automating a UI meant scripted, brittle tools tied to a specific application’s exact layout, breaking the moment that layout changed.

Once models could reliably interpret a screenshot and identify interactive elements without hardcoded rules, the category became genuinely general-purpose: an agent could attempt to operate unfamiliar software the way a person encountering it for the first time would, at least in principle.

Our coverage of the OSWorld 2.0 benchmark covers the honest version of this: scores on the original test climbed from roughly 12% to 85% in about two years, a curve steep enough to reflect the benchmark becoming saturated, not the underlying problem actually being solved. A harder version brought leading agents back down to around 20%.

Short, well-defined tasks and software with no usable API are genuinely reliable use cases now. Long, multi-app workflows with unfamiliar layouts remain the frontier. Review the benchmark directly at the OSWorld project page.

Up Next
LangChain vs LangGraph: What Differs

LangChain vs LangGraph: What Differs

Agent Frameworks

An explainer on the difference between LangChain and LangGraph, and how to decide which fits your actual agent workflow.

LangChain and LangGraph come from the same team and are often mentioned together, which leads people to assume they’re interchangeable. They solve genuinely different problems.

LangChain is a general-purpose framework for chaining together model calls, tools, and data sources, well suited to linear or moderately branching workflows: retrieval-augmented generation, straightforward multi-step chains.

LangGraph is built specifically for agent workflows that need to loop, branch conditionally, and maintain complex state across many steps, the kind of graph-shaped logic a simple linear chain can’t represent cleanly.

Sketch your actual workflow on paper first. Basically a straight line, or a simple branch? LangChain’s simpler abstraction is usually enough. Looks like a genuine graph with loops and conditional paths? LangGraph’s explicit state management saves you from working around LangChain’s more linear assumptions.

You can also use both together, LangGraph works alongside LangChain’s components rather than replacing them. Most simple agents don’t need LangGraph’s added complexity, genuinely stateful, looping agents usually do. See LangChain’s own documentation for both frameworks.