H Company introduced Holo4 on September 28, 2026, expanding its computer-use model family across graphical interfaces, code and tools. October 1 coverage followed the original launch. Downloadable weights create an evaluation option, but the Holo4-27B checkpoint carries a noncommercial license. H Company’s release provides the original date and model-family context.
The model needs an execution harness
The official model card describes a 27B vision-language model that works with the hai-agents harness. Screenshots and tool results become input; requested clicks, typing, code and tool calls are executed by the surrounding system. The model itself is not a complete desktop automation deployment.
That separation determines what an operator must evaluate. A sensible action from the model can still fail because a window moved, a tool returned stale data or the runtime clicked a different element. Preserve the state that led to the action and verify the resulting screen or tool response. A sequence of plausible clicks is not evidence that the task finished correctly.
Downloadable does not mean unrestricted commercial use
The checkpoint’s model card specifies CC BY-NC 4.0 for the weights and separately identifies the Apache 2.0 license of its base model. The base model’s permissive license does not erase the fine-tuned checkpoint’s noncommercial restriction.
Teams exploring business use should assess the actual terms applicable to the checkpoint and any hosted offering. Do not treat a quantized file or a community conversion as a new grant of rights. Record the selected model, conversion and license together so a later deployment does not lose the provenance established during evaluation.
Evaluate completion and permissions together
H Company reports benchmark results in its release materials. Those are vendor evaluations with a specific harness and cost methodology, not a guarantee for a company’s own applications. Build a small task set that includes interrupted workflows, changed layouts and cases where the agent must stop for authorization.
Use an isolated account and a reversible environment. Limit access to files and external services, then inspect both the completed artifact and any side effects. The important contribution of Holo4 is a broader model interface for computer-use experimentation. A dependable business workflow still requires an authorized execution environment, task-specific evaluation and a suitable license.