One Year of OpenHands: A Journey of Open Source AI Development marks the first anniversary of OpenHands. Written by one of the project’s early contributors and a co-founder of All Hands AI, it describes the project as having grown over the year from an ambitious idea into a thriving open-source project that is reshaping how developers interact with AI-powered coding assistants.

The post has three parts: the project’s origin story, its growth and impact over the year, and a roadmap for its second year. It ends by crediting the project’s success to open-source collaboration and inviting readers to contribute.

Key Points

  • OpenHands began on 12 March 2024 with the aim of creating an open-source AI agent for software development, so that the transformation of software development by AI would happen collaboratively, with any developer able to take part.
  • It was originally created as OpenDevin, an homage to Devin by Cognition, which the post says inspired the project in the first place. OpenDevin was created by Binyuan Hui and Junyang Lin, who are part of the team developing the Qwen open-source large language model.
  • The open-source community rallied around the project; three early contributors — Graham Neubig, Robert Brennan and Xingyao Wang — then founded All Hands AI to carry on the mission, and the project was renamed OpenHands.
  • For its first year the post reports over 50,000 GitHub stars, over 3,500 commits, more than 250 unique contributors and thousands of daily downloads of the app, and says OpenHands has been used both by individual developers automating routine tasks and by large teams on complex refactoring projects.
  • The roadmap for the second year has four items: a general release of OpenHands Cloud, then in beta; continued agent improvements, in core accuracy, on benchmarks such as SWE-Bench, and in the range of tasks handled reliably; more integrations, including a better CLI and task-management tools such as Jira and Linear; and more customization to users’ preferences, organizational policies and workflows.

Context

This is an anniversary post by the project’s own team, so its account of growth and impact is self-reported, and the figures describe the project as of March 2025.