Haiku 5.5 makes a computer for every agent practical
Haiku 5.5 uses a computer for less than half the cost of Sonnet. Your lead agent can now give each of its subagents a computer of its own.
Anthropic released Claude Haiku 5.5. It approaches Sonnet-class computer-use performance at a fraction of the cost.
What caught our eye is Haiku 5.5 scoring 72.4% on OSWorld 2.1, a benchmark for agents operating real computers, outperforming other models in cost-per-task by a big margin.
Computer-use is finally affordable
Computer use is moving from an expensive frontier-model demo toward something you can run repeatedly and at scale. On OSWorld 2.1, Haiku completes tasks while spending 50% less per attempt:
Browsing faster than any other model
OpenRouter’s current median measurements show how quickly each model generates a response:
That makes Haiku about 1.4× faster than Sonnet, 1.5× faster than Opus, and 1.8× faster than Luna. These are live provider measurements and will move over time.
See OpenRouter’s live measurements
Haiku’s natural role is the subagent
Use Opus or Sonnet to plan and make judgment calls. Delegate bounded execution to Haiku: research a record, test a flow, update a dashboard, or complete a browser task.
Ideally you would give each Haiku subagent its own computer, files, and narrowly scoped credentials, so you can run them in parallel and then return the results to the lead agent for review.
At Haiku’s price and speed, this is much cheaper and more reliable than sending one expensive model through a long workflow.
The model can click. It still needs a computer.
Anthropic developed a standard for computer-use with their defined SDKs and tool calls. An in-house SDK is likely what makes this model perform well for so few tokens; the Anthropic team had the chance to move this standard into their training data and optimize for the best use of it.
However, Haiku does not come with a computer, and the environment matters. A useful computer-use agent needs:
- An isolated machine, so one agent cannot leak into another task.
- A real browser that the model can see and control, and where the user can interrupt at any time.
- Files and state that survive longer than one API call.
Coincidentally, the Divergent team launched embedded sandboxes today.
Any agent can control an isolated computer from your server, while your user watches the screen live inside your product.
When a site requires authentication, the user can take control, sign in, and hand the browser back without exposing their password to Claude or your server.
The integration uses Anthropic’s standard computer toolset, so it works with Haiku out of the box.
See the implementation guide or start from the example app on GitHub.
What we would build now
The most compelling Haiku 5.5 applications will not look like chatbots with a cursor. They will look like small teams:
- A support agent reproducing each bug in a clean machine.
- A QA coordinator forking the same application state across test cases.
- An operations agent reconciling records across tools that have no shared API.
- A coding agent giving every implementation, test, and review subagent an isolated workspace.
Computer use has always been possible with the latest frontier models; however, Haiku makes it much more economically viable, opening up many more use cases.
We’d love to give your Haiku agent a computer. Divergent sandboxes start in under a second and run a full browser with multiple tabs. Your users can watch the agent work live with our Screen SDK.
Sources
- Anthropic: Claude Haiku 5.5 launch announcement
- Anthropic: Claude Opus 5.5 pricing
- Anthropic: Browser and computer use with the SDK toolsets
- OpenRouter: Claude Haiku 5.5 speed, latency, and pricing
- Divergent Labs: Add computer use to your product
- Divergent Labs: Computer use example app on GitHub
- Google Cloud: Provisioned Throughput for supported models
- OSWorld 2.1 benchmark notes and limitations