Key findings
- All 19 sources that discuss task execution from plan to pull request praise it. All 14 that discuss model choice are positive.
- Tasks that fail or loop are the most reported concern. Eighteen of the 23 sources that discuss task success describe loops, rate-limit stalls, failed file edits, lost cloud sessions, or a goal dropped mid-session.
- Setup comes close behind. Of 21 sources that discuss it, 17 raise problems, including Docker and WSL networking and sandboxes that fail to start on 1.x releases or on rootless Docker.
- Of 29 sources that name their models, 17 ran open-weight or local models and 12 ran hosted frontier models. Seven of the 8 sources that discuss model dependence say results rise or fall with the model, most of them about open-weight models failing on tool calls.
- Only 6 accounts speak for more than one person. Three come from company technical leaders, among them C3 AI's VP of Data Science, and the others are two small setups and ByteDance's benchmark team. OpenHands' own story of the C3 AI rollout sits outside these counts.
Engineers who ran OpenHands praise what it does once it runs, and their most common complaints are getting it to run and getting tasks to finish. That is the read of 76 English accounts published on Reddit, Hacker News, GitHub, blogs, YouTube, and arXiv between January 5, 2025 and October 25, 2026. Most still apply after OpenHands 1.0 and Agent Canvas, and this page marks the ones that do not.
Who wrote these accounts
Reddit supplies 23 posts and comments and Hacker News 19 comments. The rest are 13 GitHub issues from users outside the OpenHands team, 12 blog posts and reviews, 8 videos, and 1 independent benchmark paper. Individual builders wrote 70 of them, small multi-person setups 2, company technical leaders 3, and a research team 1. Overall, 27 are positive, 34 mixed, and 14 negative, and the benchmark paper gives no overall opinion. In 11 accounts, the authors report figures they measured themselves.
Where an account appears sets its tone. GitHub issues are bug reports, so GILD kept one per distinct problem and counted each as mixed. An issue shows a problem, and none of their authors abandoned OpenHands or advised against it. The 8 videos are all positive, and Hacker News comments run 8 positive, 6 mixed, and 5 negative.
| Where published |
|---|
| Reddit posts and comments |
| Hacker News comments |
| GitHub issues |
| Blog posts and reviews |
| Videos |
| Independent benchmark papers |
GILD review of public OpenHands accounts, n = 76, Jan 5, 2025 to Oct 25, 2026
What still applies after OpenHands 1.0 and Agent Canvas
OpenHands moved its agent onto the Software Agent SDK in OpenHands 1.0 on December 16, 2025. It archived the old local web GUI on July 27, 2026, and Agent Canvas is now its browser client. Nine accounts from 2025 that center on installing the legacy Docker runtime are marked Needs a recheck, as are ByteDance's April 2025 benchmark run on older models and Replay's January 2025 Bolt integration.
Another 57 accounts still apply as written, because the agent still runs on the model you connect, bills by the token, and works in a sandbox. The 7 accounts published since the old GUI was archived are current. Setup complaints continued after 1.0. A January 2026 GitHub issue with 61 comments reports sandboxes failing to start within 120 seconds on self-hosted 1.x installs.
Builders value execution and model choice
On a first run with Claude Sonnet 3.7, one Reddit user had OpenHands build a small WebGPU app with unit tests and serve it for about US$0.44. Another built and published a llama.cpp installer in two days with the OpenHands CLI and MiniMax M2. On Hacker News, Ancapistani used OpenHands daily for months and rates it as capable as Devin, though less polished.
Seventeen sources ran open-weight or local models, mostly Devstral and Qwen, for cost or privacy. Of 7 sources that raise model dependence, 5 describe open-weight or local models failing tool calls or forgetting to act. Two say OpenHands worked well only on Claude. In an independent benchmark, ByteDance adapted OpenHands to seven languages, and it resolved the most issues in five of them, at a higher cost per issue than the fixed-workflow Agentless.
Builders hit setup and reliability problems
Seventeen sources raise setup problems. Reddit users spent anywhere from hours to a full Saturday on Docker, WSL, and LM Studio networking. One gave up after an hour and tested the model in Roo instead. Another got OpenHands running and went back to GitHub Copilot and Aider. GitHub users report sandboxes that never start and a server deployment whose conversations never connect. Another issue describes mounted folders handed to the root group, and a self-hosted server could not start sandboxes on rootless Docker.
Eighteen sources raise task reliability. They describe loops on local models, a cloud agent stuck reading its workspace, file edits that fail on copied line numbers, and Anthropic rate limits that stall a new session. In October 2026, Cloud users reported a long session that dropped the newest goal and declared the work complete, and idle conversations that lost unpushed work. Reported costs run from about US$0.44 for a small app to about US$200 for a prototype whose token use grew late. One user saw version 0.34 spend about US$20 in five minutes.
- Pin one install method and one sandbox per team before judging results.
- Test the exact model you plan to run on tool-heavy tasks before you commit to it.
- Put a budget on every conversation from the first day.
What security reviewers flagged
Security reports name four ways an attacker or a stray model can reach beyond the task, and each belongs on a deployment review. In August 2025, security researcher wunderwuzzi published two prompt-injection attacks on OpenHands. One leaked the container's GITHUB_TOKEN through a rendered image. The other used a web page to make the agent download and run malware. A Reddit user running OpenHands offline objected to mounting the container socket, which they called equivalent to root access on the host, and OpenHands' FAQ names the same risk. In February 2026, a GitHub user saw the resolver's model open a pull request through the GitHub API with its sandbox token.
What to test in a pilot
Run the same scoped tasks on two models, one frontier and one open-weight if data rules require it, and record cost and outcome per task. Install the current Agent Canvas the way the team will run it, and time the setup. Set a budget per conversation, keep the agent's sandbox away from the Docker socket and production credentials, and compare merged pull requests against the time reviewers spent.
Methodology
GILD opened every source on October 12, 2026. It recorded the author, publisher, publication date, overall sentiment, whether figures were measured or reported, and positions taken, in the same record format GILD uses for Claude Code. A verbatim excerpt records the size of the group each source speaks for. Hacker News comments were read through the Hacker News Algolia API, Reddit posts and comments through the Arctic Shift archive with links to reddit.com, and GitHub issues through the GitHub API. Every source is in English and dated 2025 or later. GILD left out posts by All Hands AI staff, partner articles written with the OpenHands team, videos in which vendors show their own integrations, and install guides that report no results. GILD reports a finding only when at least 5 sources from 3 different authors discuss it. On October 25, 2026 GILD added ByteDance's Multi-SWE-bench paper and three October 2026 GitHub issues. The counts describe these public accounts and make no claim to represent every OpenHands user. The C3 AI figures come from OpenHands' customer story, read again on October 25, 2026.
Products in this piece
Sources
- Official documentation
- 8
- Public source
- 15
- OpenHands docs: Introduction
- OpenHands docs: Software Agent SDK
- OpenHands on GitHub: Agent Canvas (MIT)
- OpenHands legacy repository (archived)
- OpenHands docs: FAQs
- OpenHands docs: LLM overview and model recommendations
- OpenHands docs: Docker sandbox
- EternalSilverback on r/LocalLLaMA: a first run on Claude Sonnet 3.7 for about US$0.44 (May 24, 2025)
- Repulsive-Memory-298 on r/ChatGPTCoding: version 0.34 burned about US$20 of tokens in five minutes (Apr 28, 2025)
- foobarg on r/LocalLLaMA: OpenHands + Devstral is utter crap as of May 2025 (May 24, 2025)
- das_rdsm on r/LocalLLaMA: headless OpenHands deployed for several users (May 22, 2025)
- Ancapistani on Hacker News: a microagent for every architectural decision they disagree with (Aug 7, 2025)
- M. Chechulin: Open-source agentic coding systems, what can they deliver for US$10 (Sep 1, 2025)
- Daniel Manzke: Burning tokens with AI coding agents (Mar 1, 2025)
- Lior Strugach: OpenHands, your own AI employee or yet another GPT wrapper? (Jan 5, 2025)
- morgaesis, GitHub issue #11206: locally mounted folders are chowned to root (Oct 1, 2025)
- knail1, GitHub issue #9259: a new session hits Anthropic's 20,000 input tokens per minute limit (Jun 20, 2025)
- gnovak, GitHub issue #13007: the resolver opens a duplicate pull request (Feb 23, 2026)
- GitHub issue #12528: Sandbox failed to start within 120s on a self-hosted 1.2 install (Jan 21, 2026)
- wunderwuzzi, Embrace The Red: OpenHands and the lethal trifecta (Aug 9, 2025)
- wunderwuzzi, Embrace The Red: OpenHands remote code execution through prompt injection (Aug 10, 2025)
- OpenHands customer story: C3 AI (published Dec 17, 2025)
- C3 AI: Autonomous Coding Agents: Beyond Developer Productivity (Dec 24, 2025)