Holo4’s release points to a question that matters more than a single benchmark score: can one agent move between the interfaces a real task requires?
In a September 28 Hugging Face Team article, H Company announced Holo4 in 27B dense and 35B-A3B mixture-of-experts versions, alongside Holotron4 Nano. The company says the models can work through graphical interfaces, code, MCP and APIs, with the same model used across desktops, web apps, Android, code sandboxes and business systems.
That product decision is easy to understand. A business process may begin in a browser, require a short script, and then call a structured service. Choosing a separate agent for each surface adds coordination and another boundary where context can be lost. H Company’s premise is that a model that can select the appropriate interface can carry the task across those boundaries.
The evidence still needs careful reading. The article reports OSWorld 2.0 scores and AutomationBench comparisons, but it also explains that releases, harnesses and task subsets differ. For AutomationBench, some comparisons use H Company’s internal public-set runs while other points come from an official private-set leaderboard. Those figures are useful signals about the company’s evaluation program; they do not provide a clean universal ranking or prove reliability in a particular business workflow.
My recommendation is to evaluate interface switching as a failure surface. A team should ask when the model chooses code over a GUI, what permissions each route receives, and how a person can inspect an action before it changes an external system. The public trajectories may help make behavior easier to examine, but the release does not establish autonomous safety or a guarantee of successful long workflows.
Holo4’s distinct contribution is a unifying product idea: agents should be able to use the interface that matches the work. Whether that lowers total complexity depends on the quality of the routing, the safeguards around each interface, and independent results on the tasks a team actually cares about.