OpenHands v1.9.0 リリースOpenHands Releases v1.9.0

OpenHands, the open-source AI software-engineering agent formerly known as OpenDevin, has published version 1.9.0. The point release, dated August 3, 2026, focuses on a mix of platform plumbing and user-facing interface changes rather than a single headline feature, and its arrival is a useful marker of how autonomous coding agents are steadily maturing into configurable, multi-backend tools.

The most structurally significant addition is a domain-neutral extension-manifest host. In practical terms, an extension manifest is a metadata file that describes how an add-on integrates with the core application, and hosting it in a domain-neutral way means the manifest is no longer tied to a specific service address or organizational domain. This appears intended to make it easier to distribute and load extensions across different deployments, whether a user runs OpenHands as a hosted cloud service or on their own infrastructure. Decoupling the manifest from a fixed domain is the kind of change that rarely draws attention on its own but tends to be a prerequisite for a broader plugin or marketplace ecosystem later.

The release also streamlines how users choose where an agent actually runs. Version 1.9.0 introduces a more compact chooser for adding a backend, presenting the distinction between Cloud and Agent-server options in a clearer, consolidated interface. This reflects a common architectural pattern in agent platforms: the front-end chat and orchestration layer is separate from the execution backend, which can be a managed cloud environment or a self-hosted agent server. Making that selection explicit and easy to navigate matters because the backend determines where code is executed, how sandboxing is handled, and what resources the agent can reach. A cleaner chooser lowers the friction of switching between a quick cloud-based session and a locally controlled server.

On the interactivity side, the update adds live agent activity display directly in the chat interface. Rather than waiting for a task to complete or scanning separate logs, users can now watch what the agent is doing in real time within the conversation. This kind of streaming feedback has become an expected feature across the current generation of coding agents, because these systems often work autonomously for extended stretches, running commands, editing files, and browsing documentation. Surfacing that activity as it happens helps users follow the agent's reasoning, catch mistakes earlier, and decide when to intervene. The source notes additional changes beyond these, including work referenced as a mock, though the published excerpt does not fully detail it.

For context, OpenHands sits in an increasingly crowded field of AI coding agents. It competes for attention alongside tools such as GitHub Copilot's agentic modes, Cursor, Aider, Devin from Cognition, and a growing set of open-source alternatives. What distinguishes OpenHands is its open codebase and its design as a general-purpose agent that can write code, run commands in a sandbox, and interact with the web, rather than a narrow autocomplete assistant. The project is developed in the open, and releases like this one are assembled from community and maintainer contributions, with each change in the notes attributed to individual authors and pull requests.

The theme running through v1.9.0 is configurability and transparency. The extension-manifest host lays groundwork for a more modular platform, the backend chooser gives users clearer control over execution environments, and the live activity view improves visibility into an otherwise opaque process. None of these are dramatic capability leaps, but taken together they suggest a project working to make its agent easier to extend, deploy, and trust. That trajectory is consistent with the wider industry, where much of the recent engineering effort has shifted from proving that agents can complete tasks toward making them safe, observable, and adaptable to different workflows.

Users on existing installations will generally pick up these changes by updating to the tagged 1.9.0 version through their usual distribution channel, whether that is a container image, a package, or the hosted service. As always with point releases, teams relying on custom extensions or specific backend configurations should review the full changelog before upgrading, since interface and manifest-handling changes can affect existing setups. The complete list of merged pull requests is available in the project's release notes.