76 sources from practitioners, by month and sentiment.
The read is mixed, and one benchmark paper gives no overall opinion. Every source that discusses end-to-end execution or model choice praises it. Unreliable tasks draw the most concerns, and setup friction follows in 17 sources.
Positive, mixed and negative sources
211912
The score counts them as 18 positive, 18 mixed and 11 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 76 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1End-to-end executionAll 17 sources on it praise itPlanning, editing, running commands and tests, and iterating to a working result or pull request without step-by-step prompting.
Agent Canvas planned, coded, tested and documented a dependency-free Python gradebook; Today's AI verifies the tests and stresses that human review is still needed.
"Uh you can see that Asent Canvas can automate planning, coding, testing. But, human review still necessary. Uh the user basically responsible for defining the scope, project secret, inspecting general code, and deciding whether the evidence is sufficient."
On a VPS-hosted OpenHands using Claude Sonnet 4.6 through OpenRouter, the agent read a GitHub issue about completed to-dos showing as pending and a reversed priority sort, fixed the get-pending function, reported five tests passed and opened a pull request the author merged.
"So, you can see this pull request. I did not write it. It was written by OpenHands. This is an open-source AI that uh it read the broken repo, found the bug, fixed it, and then opened this PR by itself. Okay? Then I went…"
Published Jun 23, 2026self-described: Solo; deployed OpenHands on a Hostinger VPS (video sponsored by Hostinger) and gave it a real bug in a test repository
Practitioner account, self-described; direct use; counts toward Operational control, Cost predictability and limits
Ran headless OpenHands on a Vast.ai VM with Ollama serving a Qwen3-family coding model. The GUI looked fine when it was not, the first autonomous runs exposed fake progress, and progress controllers and driver scripts were needed before a final burst ended with 48 passing tests and a stable MVP.
Published Apr 8, 2026self-described: Solo experiment: unattended multi-run build of a Python product on a disposable Vast.ai GPU VM
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
OpenHands migrated their blog to a new framework with a plan step and a running local build, needing a few prompts and small manual fixes; Isaac Flath calls the experience largely positive.
Published Jul 30, 2025self-described: Solo; migrating their Quarto blog to the Air web framework via OpenHands connected to GitHub
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Adoption and upkeep
Positive
Isaac Flath, Independent consultant (YouTube channel)
Isaac Flath's video review follows a smooth migration from voice-prompted setup to a successful result, with minor issues to steer past.
"…was migrating the blog. It was pretty positive. It wasn't fully autonomous. I never really expect these things to be completely hands-off where I don't have to think at all or do anything at all. I always hope they will be, but…"
On their first run, OpenHands with Claude Sonnet 3.7 built a small WebGPU app with unit tests and served it for review for about US$0.44. Their attempt with a local model failed to start.
Published May 24, 2025self-described: First run, Claude Sonnet 3.7
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits
Trying OpenHands with Devstral, Mr_Moonsilver was impressed by how capable the agent is and finds it as capable as the other top open-source coding agents.
Published May 22, 2025self-described: Tried OpenHands with Mistral's Devstral
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
No opinion stated
ByteDance Seed research team, authors of Multi-SWE-bench
ByteDance adapted OpenHands to Java, TypeScript, JavaScript, Go, Rust, C, and C++ and ran it against Agentless and SWE-agent on 1,632 issues. OpenHands had the highest resolve rate in five of the seven languages, and its model-driven workflow took more turns and cost more than fixed-workflow Agentless.
"Overall, MopenHands outperforms the others in most cases, achieving the highest resolved rate in five out of seven languages, while MSWE-agent wins twice and MagentLess wins once."
Excerpt, ByteDance Seed
Published Apr 3, 2025self-described: Research team at ByteDance running an adapted OpenHands (MopenHands) on 1,632 issues in seven languages with nine models
Sets up self-hosted OpenHands with an Anthropic model and a GitHub repo. From single prompts it builds a website for the channel, which picked up the wrong Jim's Garage when customized, and a working Hello World app; says one simple prompt built a working website within a few seconds.
"…change the greeting to different languages as we' seen in the background it also keeps a click counter which is possibly cool but anyway you can see how from one simple prompt I was able to build a working website within a few seconds so…"
Xper runs an OpenHands-based agent environment in its own cloud for DocEngine. Agents take tasks from GitHub Issues, open a pull request, review and fix their own change in a repeated loop, and a human approves the merge before automatic deployment.
"We now run an OpenHands-based agent environment in our own cloud. We have one place to change the context our agents use, their skills, and their plugins."
Excerpt, Tomas Hajek
"It reviews the change, fixes the issues it finds, and runs that review-and-fix loop again."
Same speaker
Published Sep 17, 2026self-described: Norwegian document-automation consultancy building its DocEngine product with agents in its own cloud
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control
Mixed
M. Chechulin, Senior Lead Software Developer at a mid-to-large company in Germany
Gave OpenHands, Cline and Goose US$10 each; OpenHands was the most stable (3 of 5, partial success) but overspent to US$14.97 and most often ignored instructions.
Published Sep 1, 2025self-described: Pet project (Firefox chat-with-page extension), each tool given a US$10 Anthropic API budget; compared with Cline and Goose
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Cost predictability and limits, Adoption and upkeep
Has used OpenHands daily for months, locally, via CLI and in the cloud; says it is less polished than Devin but as capable, and the team is responsive to feedback.
Published Aug 30, 2025self-described: Uses OpenHands daily in local, CLI and cloud setups
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Runs OpenHands locally, has it write and run a Hacker News bash script that it debugs on its own; likes local open-source use but flags the freedom it gets on the machine.
"Pro uh M2 Chip I think um you can see runs locally Port 3000 and um it's got integration to vs code over here um and I just asked the the coder um the the AI agent to please write a bash script which displays…"
In a company trial OpenHands failed to build an API layer after thirty minutes, but wrote internal READMEs and test coverage well; best for routine, well-defined tasks.
Published Jan 5, 2025self-described: Evaluated against typical development scenarios in their (unnamed) company environment
2Model choiceAll 14 sources on it praise itRunning the agent on the model or provider the team chooses, from frontier APIs to open-weight models served locally, and switching between them.
Trying the model from the thread: Qwen Code fails to use tools and crashes, Aider was a huge waste of time, and OpenHands is working really well apart from occasional malformed str_replace tool-call errors. The jury is still out on whether it beats Devstral.
Published Jul 31, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Points to open alternatives to Claude Code that run in any environment with any model and on your own economics, naming OpenHands and Codex CLI as current favorites.
Published Jul 13, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Finds the new OpenHands CLI fast and lightweight, and as agentic as Claude Code with Gemini 2.5 Pro. Notes it lacks MCP support and an SDK at the time.
"…similar to claude code and ader. So that is good but that doesn't mean that it is the best because there are quite some shortcomings like a major one is that it doesn't support MCP. Yes, you can't add the MCP servers and…"
Ran Mistral's Devstral locally in LM Studio with OpenHands and Cline and says it worked great in both, with about one minute of initial prompt processing on an M4 Max.
Published May 22, 2025self-described: Runs Devstral on an M4 Max using LM Studio
Practitioner account, pseudonymous; direct use; counts toward Operational control
Built an ecommerce web UI with OpenHands 0.26 and Claude for around US$5-$6, getting rate limited by Anthropic every time a command was sent. Things were slow, downloading the code from the UI never completed, and the author warns to push often because nothing stops OpenHands deleting files.
Published Mar 4, 2025self-described: Solo; built an ecommerce web app in the OpenHands web UI
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
On a VPS-hosted OpenHands using Claude Sonnet 4.6 through OpenRouter, the agent read a GitHub issue about completed to-dos showing as pending and a reversed priority sort, fixed the get-pending function, reported five tests passed and opened a pull request the author merged.
"So, you can see this pull request. I did not write it. It was written by OpenHands. This is an open-source AI that uh it read the broken repo, found the bug, fixed it, and then opened this PR by itself. Okay? Then I went…"
Published Jun 23, 2026self-described: Solo; deployed OpenHands on a Hostinger VPS (video sponsored by Hostinger) and gave it a real bug in a test repository
Practitioner account, self-described; direct use; counts toward Operational control, Cost predictability and limits
Rybens92 calls OpenHands the best alternative to proprietary coding agents and runs it on a US$10 or US$20 Chutes.ai subscription to avoid paying per token.
Published Aug 27, 2025self-described: Personal use on a Chutes.ai model subscription
Practitioner account, pseudonymous; opinion; not counted, takes no position
The OpenHands CLI works well for tbiens with Devstral; Qwen3 Coder works 80 to 90% of the time but sometimes fails file edits with a malformed tool call.
Published Aug 1, 2025self-described: OpenHands CLI 0.50.0 with local models
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Finds OpenHands delightfully good with clear instructions and a free Gemini model, but self-hosting on Kubernetes took several attempts and needs a privileged pod with the Docker socket.
Published Feb 24, 2025self-described: Solo; ran OpenHands locally, then self-hosted it on their own Kubernetes cluster
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Positive
sentdex, YouTube creator (Python and ML programming)
Uses OpenHands 0.23 with Claude 3.5 Sonnet (transcribed "CLA onic 3.5") and calls these tools massive amplifications of the author's output, worth paying for. Notes the download-all-files button lately does not work, so the author asks the agent to zip the workspace instead.
"…annoyed at everything is like 20 bucks a month um but for the most part uh all these things are like massive amplifications of my my actual output so I do think it's worth it but just because I don't I don't really want to…"
3Open source & self-hosting9 of 10 sources on it praise itAn agent the team can inspect, extend, and run on its own machines or infrastructure under the MIT license.
Counted for All practitioners.
Positive, 9
Positive
Tomas Hajek, co-founder, managing consultant, and lead architect at Xper Consulting AS
Xper runs an OpenHands-based agent environment in its own cloud for DocEngine. Agents take tasks from GitHub Issues, open a pull request, review and fix their own change in a repeated loop, and a human approves the merge before automatic deployment.
"We now run an OpenHands-based agent environment in our own cloud. We have one place to change the context our agents use, their skills, and their plugins."
Excerpt, Tomas Hajek
"It reviews the change, fixes the issues it finds, and runs that review-and-fix loop again."
Same speaker
Published Sep 17, 2026self-described: Norwegian document-automation consultancy building its DocEngine product with agents in its own cloud
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control
Has used OpenHands a ton since November, when it led SWE-bench, and says "afaik no other os comes close", though its lead didn't last. Finds it pretty bloated for local use next to newer tooling, depending on the use case, and very easy to customize with agents and microagents.
Published May 23, 2025self-described: Heavy use since November 2024
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Finds OpenHands delightfully good with clear instructions and a free Gemini model, but self-hosting on Kubernetes took several attempts and needs a privileged pod with the Docker socket.
Published Feb 24, 2025self-described: Solo; ran OpenHands locally, then self-hosted it on their own Kubernetes cluster
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Runs OpenHands locally, has it write and run a Hacker News bash script that it debugs on its own; likes local open-source use but flags the freedom it gets on the machine.
"Pro uh M2 Chip I think um you can see runs locally Port 3000 and um it's got integration to vs code over here um and I just asked the the coder um the the AI agent to please write a bash script which displays…"
On a VPS-hosted OpenHands using Claude Sonnet 4.6 through OpenRouter, the agent read a GitHub issue about completed to-dos showing as pending and a reversed priority sort, fixed the get-pending function, reported five tests passed and opened a pull request the author merged.
"So, you can see this pull request. I did not write it. It was written by OpenHands. This is an open-source AI that uh it read the broken repo, found the bug, fixed it, and then opened this PR by itself. Okay? Then I went…"
Published Jun 23, 2026self-described: Solo; deployed OpenHands on a Hostinger VPS (video sponsored by Hostinger) and gave it a real bug in a test repository
Practitioner account, self-described; direct use; counts toward Operational control, Cost predictability and limits
Running OpenHands in Docker as one agent under a local orchestrator, Smooth-Pipe6285 has the web UI working but cannot find the API endpoint to connect it over ACP.
Published Mar 29, 2026self-described: Local homelab with an orchestrator, Docker, and a DGX Spark
Practitioner account, pseudonymous; ran the rollout; counts toward Adoption and upkeep
Points to open alternatives to Claude Code that run in any environment with any model and on your own economics, naming OpenHands and Codex CLI as current favorites.
Published Jul 13, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Trying OpenHands with Devstral, Mr_Moonsilver was impressed by how capable the agent is and finds it as capable as the other top open-source coding agents.
Published May 22, 2025self-described: Tried OpenHands with Mistral's Devstral
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
das_rdsm runs OpenHands headless and fully autonomous for several users, calls it a full software-engineering agent that Roo and Cline do not match, and also uses it for non-coding tasks.
Published May 22, 2025self-described: Headless OpenHands deployed for several users
Practitioner account, pseudonymous; ran the rollout; counts toward Delivered outcomes, Operational control
Deployed on a dedicated server, the web interface loads but no conversation starts, because the worker container tries to connect on localhost when it should use the server's address.
Published Jan 30, 2026self-described: OpenHands 1.2.1 on a dedicated Docker server
Practitioner account, pseudonymous; ran the rollout; counts toward Adoption and upkeep
Finds the new OpenHands CLI fast and lightweight, and as agentic as Claude Code with Gemini 2.5 Pro. Notes it lacks MCP support and an SDK at the time.
"…similar to claude code and ader. So that is good but that doesn't mean that it is the best because there are quite some shortcomings like a major one is that it doesn't support MCP. Yes, you can't add the MCP servers and…"
Uses OpenHands 0.23 with Claude 3.5 Sonnet (transcribed "CLA onic 3.5") and calls these tools massive amplifications of the author's output, worth paying for. Notes the download-all-files button lately does not work, so the author asks the agent to zip the workspace instead.
"…annoyed at everything is like 20 bucks a month um but for the most part uh all these things are like massive amplifications of my my actual output so I do think it's worth it but just because I don't I don't really want to…"
Ancapistani uses OpenHands Cloud as their primary coding agent and adds a microagent whenever it makes an architectural choice they disagree with. The setup aligns OpenHands with their preferences over time.
Published Aug 7, 2025self-described: Uses OpenHands microagents with organization-level configurations
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
Isaac Flath, Independent consultant (per Substack author profile)
OpenHands migrated their blog to a new framework with a plan step and a running local build, needing a few prompts and small manual fixes; Isaac Flath calls the experience largely positive.
Published Jul 30, 2025self-described: Solo; migrating their Quarto blog to the Air web framework via OpenHands connected to GitHub
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Adoption and upkeep
Positive
Isaac Flath, Independent consultant (YouTube channel)
Isaac Flath's video review follows a smooth migration from voice-prompted setup to a successful result, with minor issues to steer past.
"…was migrating the blog. It was pretty positive. It wasn't fully autonomous. I never really expect these things to be completely hands-off where I don't have to think at all or do anything at all. I always hope they will be, but…"
Spent about US$200 in tokens building a prototype. Token use exploded late as files were regenerated and the codebase ballooned. Finds it great for prototyping and unready for complex products.
Published Mar 1, 2025self-described: Weekend prototype of a Q&A app against their company's enterprise search APIs
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Spent a few days with OpenHands on gpt-4o: decent at writing new code and transparent in the terminal, but struggled to change repetitive TypeScript/React code.
Published Jan 26, 2025self-described: Solo, TypeScript/React project created with Vite
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Runs OpenHands locally, has it write and run a Hacker News bash script that it debugs on its own; likes local open-source use but flags the freedom it gets on the machine.
"Pro uh M2 Chip I think um you can see runs locally Port 3000 and um it's got integration to vs code over here um and I just asked the the coder um the the AI agent to please write a bash script which displays…"
Describes OpenHands as a locally run, Codex or Claude Code style web UI for remote LLMs, but calls it clunky, limited and poorly designed, preferring OpenCode's web UI.
Published Apr 30, 2026self-described: Remote information systems engineering professional
Practitioner account, pseudonymous; opinion; not counted, takes no position
Built an ecommerce web UI with OpenHands 0.26 and Claude for around US$5-$6, getting rate limited by Anthropic every time a command was sent. Things were slow, downloading the code from the UI never completed, and the author warns to push often because nothing stops OpenHands deleting files.
Published Mar 4, 2025self-described: Solo; built an ecommerce web app in the OpenHands web UI
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Ran headless OpenHands on a Vast.ai VM with Ollama serving a Qwen3-family coding model. The GUI looked fine when it was not, the first autonomous runs exposed fake progress, and progress controllers and driver scripts were needed before a final burst ended with 48 passing tests and a stable MVP.
Published Apr 8, 2026self-described: Solo experiment: unattended multi-run build of a Python product on a disposable Vast.ai GPU VM
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Has used OpenHands daily for months, locally, via CLI and in the cloud; says it is less polished than Devin but as capable, and the team is responsive to feedback.
Published Aug 30, 2025self-described: Uses OpenHands daily in local, CLI and cloud setups
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Running OpenHands offline with Devstral on a 24GB GPU, foobarg found the configuration broken and undocumented, objected to mounting the container socket, and saw Devstral fail almost every basic task.
Published May 24, 2025self-described: Fully offline setup: Devstral Q4_K_M on Ollama, OpenHands in podman
yeldarb tried OpenHands in their own codebase a couple of months earlier and found it frustrating, expensive, and no faster than doing the task themselves.
Published Jan 23, 2025self-described: Own codebase, day-to-day work
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
5Async delegation4 of 6 sources on it praise itHanding off an issue from GitHub, Slack, Jira, or an automation and getting a pull request back without watching the conversation.
Counted for All practitioners.
Positive, 4
Positive
Tomas Hajek, co-founder, managing consultant, and lead architect at Xper Consulting AS
Xper runs an OpenHands-based agent environment in its own cloud for DocEngine. Agents take tasks from GitHub Issues, open a pull request, review and fix their own change in a repeated loop, and a human approves the merge before automatic deployment.
"We now run an OpenHands-based agent environment in our own cloud. We have one place to change the context our agents use, their skills, and their plugins."
Excerpt, Tomas Hajek
"It reviews the change, fixes the issues it finds, and runs that review-and-fix loop again."
Same speaker
Published Sep 17, 2026self-described: Norwegian document-automation consultancy building its DocEngine product with agents in its own cloud
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control
On a VPS-hosted OpenHands using Claude Sonnet 4.6 through OpenRouter, the agent read a GitHub issue about completed to-dos showing as pending and a reversed priority sort, fixed the get-pending function, reported five tests passed and opened a pull request the author merged.
"So, you can see this pull request. I did not write it. It was written by OpenHands. This is an open-source AI that uh it read the broken repo, found the bug, fixed it, and then opened this PR by itself. Okay? Then I went…"
Published Jun 23, 2026self-described: Solo; deployed OpenHands on a Hostinger VPS (video sponsored by Hostinger) and gave it a real bug in a test repository
Practitioner account, self-described; direct use; counts toward Operational control, Cost predictability and limits
Comparing asynchronous agents on issue-to-pull-request work, intellectronica rated OpenHands capable but in need of nudges on tests and CI, behind GitHub Copilot's agent on reliability.
Published Aug 19, 2025self-described: Comparison of asynchronous coding agents on issue-to-pull-request work
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
das_rdsm runs OpenHands headless and fully autonomous for several users, calls it a full software-engineering agent that Roo and Cline do not match, and also uses it for non-coding tasks.
Published May 22, 2025self-described: Headless OpenHands deployed for several users
Practitioner account, pseudonymous; ran the rollout; counts toward Delivered outcomes, Operational control
With the GitHub resolver on claude-opus-4-5, the model opened its own pull request through the GitHub API with the token in its sandbox, and the resolver then opened a second one.
Published Feb 23, 2026self-described: OpenHands GitHub resolver with claude-opus-4-5
Practitioner account, pseudonymous; direct use; counts toward Reliability
Running the resolver in GitHub Actions, file edits often fail because the agent copies line numbers from cat -n into its replacements; an instructions file did little to stop it.
Published Apr 16, 2025self-described: OpenHands GitHub resolver in GitHub Actions
Practitioner account, pseudonymous; direct use; counts toward Reliability
Ran Mistral's Devstral locally in LM Studio with OpenHands and Cline and says it worked great in both, with about one minute of initial prompt processing on an M4 Max.
Published May 22, 2025self-described: Runs Devstral on an M4 Max using LM Studio
Practitioner account, pseudonymous; direct use; counts toward Operational control
The OpenHands CLI works well for tbiens with Devstral; Qwen3 Coder works 80 to 90% of the time but sometimes fails file edits with a malformed tool call.
Published Aug 1, 2025self-described: OpenHands CLI 0.50.0 with local models
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Trying the model from the thread: Qwen Code fails to use tools and crashes, Aider was a huge waste of time, and OpenHands is working really well apart from occasional malformed str_replace tool-call errors. The jury is still out on whether it beats Devstral.
Published Jul 31, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Every concern practitioners raise, most raised first.
1Unpredictable task success18 of 23 sources on it raise it as a concernConversations that fail, loop, or stall, and difficulty predicting which tasks will finish.
Counted for All practitioners.
Raised as a concern, 18
Mixed
vwart, GitHub user filing an issue against OpenHands/OpenHands
On OpenHands Cloud, nearly every conversation left idle for about 20 minutes could no longer reach its server, and work not yet pushed was lost along with the tokens spent on it.
"Nearly every conversation reaches a state in which it is "unable to connect to server" forever. Mostly not having pushed anything, so all the work and tokens that were used are lost."
Excerpt, vwart
Published Oct 25, 2026self-described: OpenHands Cloud on macOS, latest Agent Canvas
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
shukriaprinters, GitHub user filing an issue against OpenHands/OpenHands
In a long OpenHands Cloud session, the agent dropped the user's newest goal, went back to an older security-audit task, and reported all work complete while a named deliverable was still unbuilt.
"The agent silently abandoned the user's **current** goal and reverted to an **older** instruction context, then reported the task as complete while a named deliverable was still missing."
Excerpt, shukriaprinters
Published Oct 23, 2026self-described: Private TypeScript project on OpenHands Cloud, one session past 4,355 events and 20 condensations
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Long OpenHands sessions on local Qwen and GLM models in LM Studio bring memory failures, model looping, broken tool calls, and even full reboots. The user juaps suspects LM Studio more than any one model.
Published Mar 10, 2026self-described: Local models in LM Studio on a 48GB Mac
Practitioner account, pseudonymous; direct use; not counted, takes no position
Asked to add an HTML page, the agent failed every file edit with a missing-parameter error on claude-sonnet-4; switching to qwen3-coder-plus cleared it after one error.
Published Sep 4, 2025self-described: OpenHands 0.55
Practitioner account, pseudonymous; direct use; counts toward Reliability
Even a brand-new session with a simple command hits Anthropic's 20,000 input tokens per minute limit for their organization, so OpenHands stalls on rate-limit errors.
Published Jun 20, 2025self-described: Anthropic API key in OpenHands
Practitioner account, pseudonymous; direct use; counts toward Reliability
On Devstral with a 131k context, OpenHands went into loops; switching to manual confirmation mode made it much better, and iSevenDays calls it a great project with a few bugs to fix.
Published May 25, 2025self-described: Devstral with a 131k context
Practitioner account, pseudonymous; direct use; counts toward Reliability, Operational control
Running the resolver in GitHub Actions, file edits often fail because the agent copies line numbers from cat -n into its replacements; an instructions file did little to stop it.
Published Apr 16, 2025self-described: OpenHands GitHub resolver in GitHub Actions
Practitioner account, pseudonymous; direct use; counts toward Reliability
Tested OpenHands a few times and found it fails fairly quickly, getting hung up while setting up Kotlin and Go projects and hitting Claude rate limits fast.
Published Feb 24, 2025self-described: Kotlin and Go test projects
Practitioner account, pseudonymous; direct use; counts toward Reliability
Spent a few days with OpenHands on gpt-4o: decent at writing new code and transparent in the terminal, but struggled to change repetitive TypeScript/React code.
Published Jan 26, 2025self-described: Solo, TypeScript/React project created with Vite
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
In a company trial OpenHands failed to build an API layer after thirty minutes, but wrote internal READMEs and test coverage well; best for routine, well-defined tasks.
Published Jan 5, 2025self-described: Evaluated against typical development scenarios in their (unnamed) company environment
Both official installs on Debian 13, uv and Docker, hung on a spinning wheel because OpenHands could not connect to a sandbox. On the open issue, nealhamiltonjr saw no reply from the team.
Published Feb 23, 2026self-described: Debian 13, official uv and Docker installs
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
On OpenHands 1.2 installed with the README Docker command, conversations fail with "Sandbox failed to start within 120s". It sometimes starts normally, and for some repos and branches it starts fine while others time out.
Published Jan 21, 2026self-described: Self-hosted OpenHands 1.x
Practitioner account, pseudonymous; direct use; counts toward Reliability
Lists questions the author asks before handing work to an agent, given an AGENTS.md file, such as whether the agent can verify the solution itself and whether the starting context is enough. Recalls Claude and OpenHands instantly digging themselves holes before the author realized there was zero project context.
Published Jul 10, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Running OpenHands on local Devstral, simple prompts such as building a React button component usually fail: the model creates no files and tells the user to create them.
Published Jun 6, 2025self-described: Local Devstral, a new create-react-app repository
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Devstral through OpenRouter works well in OpenHands when it works but sometimes loops; on their limited hardware Amazing_Athlete_2265 prefers Aider, which lets Amazing_Athlete_2265 control context size.
Published May 25, 2025self-described: Limited local hardware; Devstral through OpenRouter
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
Built an ecommerce web UI with OpenHands 0.26 and Claude for around US$5-$6, getting rate limited by Anthropic every time a command was sent. Things were slow, downloading the code from the UI never completed, and the author warns to push often because nothing stops OpenHands deleting files.
Published Mar 4, 2025self-described: Solo; built an ecommerce web app in the OpenHands web UI
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Mixed
Daniel Manzke, Medium (works on an enterprise search product)
Spent about US$200 in tokens building a prototype. Token use exploded late as files were regenerated and the codebase ballooned. Finds it great for prototyping and unready for complex products.
Published Mar 1, 2025self-described: Weekend prototype of a Q&A app against their company's enterprise search APIs
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Discussed without concern, 5
Mixed
M. Chechulin, Senior Lead Software Developer at a mid-to-large company in Germany
Gave OpenHands, Cline and Goose US$10 each; OpenHands was the most stable (3 of 5, partial success) but overspent to US$14.97 and most often ignored instructions.
Published Sep 1, 2025self-described: Pet project (Firefox chat-with-page extension), each tool given a US$10 Anthropic API budget; compared with Cline and Goose
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Cost predictability and limits, Adoption and upkeep
Comparing asynchronous agents on issue-to-pull-request work, intellectronica rated OpenHands capable but in need of nudges on tests and CI, behind GitHub Copilot's agent on reliability.
Published Aug 19, 2025self-described: Comparison of asynchronous coding agents on issue-to-pull-request work
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Trying the model from the thread: Qwen Code fails to use tools and crashes, Aider was a huge waste of time, and OpenHands is working really well apart from occasional malformed str_replace tool-call errors. The jury is still out on whether it beats Devstral.
Published Jul 31, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Positive
sentdex, YouTube creator (Python and ML programming)
Uses OpenHands 0.23 with Claude 3.5 Sonnet (transcribed "CLA onic 3.5") and calls these tools massive amplifications of the author's output, worth paying for. Notes the download-all-files button lately does not work, so the author asks the agent to zip the workspace instead.
"…annoyed at everything is like 20 bucks a month um but for the most part uh all these things are like massive amplifications of my my actual output so I do think it's worth it but just because I don't I don't really want to…"
Published Feb 15, 2025self-described: Solo; hour-long session building projects with OpenHands
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.OpenHands' guidance rates bug fixes with reproduction steps, test additions, and changes that follow existing patterns as the best fit. It asks for large refactors and architectural changes to be split into phases. When to use OpenHands
2Setup & runtime friction17 of 21 sources on it raise it as a concernWork to install and configure the Docker runtime, the sandbox, local models, and each repository's environment.
Counted for All practitioners.
Raised as a concern, 17
Mixed
thelodge-network, GitHub user filing an issue against OpenHands/OpenHands
Self-hosted on a rootless Docker daemon, OpenHands could not start conversation sandboxes: each exited with a permission error and the server returned 502. Tests showed the sandbox ran when the mounts were opened or the container ran as uid 0.
"The sandbox exits 1 with a `PermissionError: [Errno 13]` trying to stat `workspace/openhands_agent_server_config.json` inside the bind mount…"
Excerpt, thelodge-network
Published Oct 17, 2026self-described: Self-hosted OpenHands agent server on a rootless Docker daemon
Ran headless OpenHands on a Vast.ai VM with Ollama serving a Qwen3-family coding model. The GUI looked fine when it was not, the first autonomous runs exposed fake progress, and progress controllers and driver scripts were needed before a final burst ended with 48 passing tests and a stable MVP.
Published Apr 8, 2026self-described: Solo experiment: unattended multi-run build of a Python product on a disposable Vast.ai GPU VM
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Running OpenHands in Docker as one agent under a local orchestrator, Smooth-Pipe6285 has the web UI working but cannot find the API endpoint to connect it over ACP.
Published Mar 29, 2026self-described: Local homelab with an orchestrator, Docker, and a DGX Spark
Practitioner account, pseudonymous; ran the rollout; counts toward Adoption and upkeep
Both official installs on Debian 13, uv and Docker, hung on a spinning wheel because OpenHands could not connect to a sandbox. On the open issue, nealhamiltonjr saw no reply from the team.
Published Feb 23, 2026self-described: Debian 13, official uv and Docker installs
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Deployed on a dedicated server, the web interface loads but no conversation starts, because the worker container tries to connect on localhost when it should use the server's address.
Published Jan 30, 2026self-described: OpenHands 1.2.1 on a dedicated Docker server
Practitioner account, pseudonymous; ran the rollout; counts toward Adoption and upkeep
On OpenHands 1.2 installed with the README Docker command, conversations fail with "Sandbox failed to start within 120s". It sometimes starts normally, and for some repos and branches it starts fine while others time out.
Published Jan 21, 2026self-described: Self-hosted OpenHands 1.x
Practitioner account, pseudonymous; direct use; counts toward Reliability
Running locally with a mounted folder, each new conversation creates an unwanted git repository and gives the folder and every agent-created file to group root, so morgaesis runs chown by hand.
Published Oct 1, 2025self-described: Local Docker install with a mounted project folder, OpenHands 0.57
Practitioner account, pseudonymous; direct use; counts toward Operational control
Getting OpenHands to run with LM Studio on Windows 11 and WSL2 took a whole Saturday of Docker and network workarounds. The result was underwhelming next to GitHub Copilot agent mode or Aider.
Published May 25, 2025self-described: Windows 11 with WSL2 and LM Studio
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Running OpenHands offline with Devstral on a 24GB GPU, foobarg found the configuration broken and undocumented, objected to mounting the container socket, and saw Devstral fail almost every basic task.
Published May 24, 2025self-described: Fully offline setup: Devstral Q4_K_M on Ollama, OpenHands in podman
FullstackSensei wanted to test Devstral in OpenHands but found it hard to run outside Docker or to set up with their own API. They gave up after about an hour and used Roo instead.
Published May 22, 2025self-described: Testing Devstral locally
Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep
Getting OpenHands running on Windows with WSL took two pages of documentation and a long Docker command, and an attached existing project still showed a not-a-git-repository warning.
Published May 22, 2025self-described: Windows with WSL, OpenHands 0.39 in Docker
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Finds OpenHands delightfully good with clear instructions and a free Gemini model, but self-hosting on Kubernetes took several attempts and needs a privileged pod with the Docker socket.
Published Feb 24, 2025self-described: Solo; ran OpenHands locally, then self-hosted it on their own Kubernetes cluster
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Long OpenHands sessions on local Qwen and GLM models in LM Studio bring memory failures, model looping, broken tool calls, and even full reboots. The user juaps suspects LM Studio more than any one model.
Published Mar 10, 2026self-described: Local models in LM Studio on a 48GB Mac
Practitioner account, pseudonymous; direct use; not counted, takes no position
Mixed
M. Chechulin, Senior Lead Software Developer at a mid-to-large company in Germany
Gave OpenHands, Cline and Goose US$10 each; OpenHands was the most stable (3 of 5, partial success) but overspent to US$14.97 and most often ignored instructions.
Published Sep 1, 2025self-described: Pet project (Firefox chat-with-page extension), each tool given a US$10 Anthropic API budget; compared with Cline and Goose
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Cost predictability and limits, Adoption and upkeep
b1uedust runs OpenHands with LM Studio on a Mac mini and a 3080 Ti. Quantized 7B and 13B models held up on the Mac, larger ones were slow, and b1uedust is pricing a dedicated GPU.
Published Jul 24, 2025self-described: Self-hosted homelab: OpenHands with LM Studio on an M4 Pro Mac mini and a 3080 Ti
Practitioner account, pseudonymous; direct use; counts toward Operational control
On their first run, OpenHands with Claude Sonnet 3.7 built a small WebGPU app with unit tests and served it for review for about US$0.44. Their attempt with a local model failed to start.
Published May 24, 2025self-described: First run, Claude Sonnet 3.7
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits
Ran Mistral's Devstral locally in LM Studio with OpenHands and Cline and says it worked great in both, with about one minute of initial prompt processing on an M4 Max.
Published May 22, 2025self-described: Runs Devstral on an M4 Max using LM Studio
Practitioner account, pseudonymous; direct use; counts toward Operational control
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Since OpenHands 1.0 the agent runs in a Docker, process, or remote sandbox through the Agent Server. Agent Canvas installs with npm or a single Docker command, and accounts of the legacy Docker runtime describe the earlier setup. Sandbox overview
Gave OpenHands, Cline and Goose US$10 each; OpenHands was the most stable (3 of 5, partial success) but overspent to US$14.97 and most often ignored instructions.
Published Sep 1, 2025self-described: Pet project (Firefox chat-with-page extension), each tool given a US$10 Anthropic API budget; compared with Cline and Goose
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Cost predictability and limits, Adoption and upkeep
Mixed
jacobson_engineering, Reddit user in r/ChatGPTCoding
Building web apps with OpenHands, jacobson_engineering finds it works well only on Claude and needs a budget of at least US$50 in API spend to run without problems.
Published Aug 28, 2025self-described: Building web apps with OpenHands and Replit
Practitioner account, pseudonymous; direct use; counts toward Operational control, Cost predictability and limits
Even a brand-new session with a simple command hits Anthropic's 20,000 input tokens per minute limit for their organization, so OpenHands stalls on rate-limit errors.
Published Jun 20, 2025self-described: Anthropic API key in OpenHands
Practitioner account, pseudonymous; direct use; counts toward Reliability
Mixed
Repulsive-Memory-298, Reddit user in r/ChatGPTCoding
OpenHands had been solid for Repulsive-Memory-298 since November, but version 0.34 burned about US$20 of Anthropic tokens in five minutes on a small project.
Published Apr 28, 2025self-described: Use since November 2024 on Anthropic models
Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits
Built a personal RAG system over three weekends with OpenHands and Trae in Docker for about US$60; rated satisfaction around 10% and spent more time debugging than building.
Published Mar 31, 2025self-described: Solo weekend project
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
Daniel Manzke, Medium (works on an enterprise search product)
Spent about US$200 in tokens building a prototype. Token use exploded late as files were regenerated and the codebase ballooned. Finds it great for prototyping and unready for complex products.
Published Mar 1, 2025self-described: Weekend prototype of a Q&A app against their company's enterprise search APIs
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Using the model under discussion with OpenHands to write a simple web crawler for a hobby RAG project, found it great but quite expensive at about US$8 an hour. In Trea it was pretty bad but free; the author asks, "Maybe it depends on how the agents use it?"
Published Feb 22, 2025self-described: Solo hobby RAG project
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
yeldarb tried OpenHands in their own codebase a couple of months earlier and found it frustrating, expensive, and no faster than doing the task themselves.
Published Jan 23, 2025self-described: Own codebase, day-to-day work
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
vwart, GitHub user filing an issue against OpenHands/OpenHands
On OpenHands Cloud, nearly every conversation left idle for about 20 minutes could no longer reach its server, and work not yet pushed was lost along with the tokens spent on it.
"Nearly every conversation reaches a state in which it is "unable to connect to server" forever. Mostly not having pushed anything, so all the work and tokens that were used are lost."
Excerpt, vwart
Published Oct 25, 2026self-described: OpenHands Cloud on macOS, latest Agent Canvas
Practitioner account, pseudonymous; direct use; counts toward Reliability
Built an ecommerce web UI with OpenHands 0.26 and Claude for around US$5-$6, getting rate limited by Anthropic every time a command was sent. Things were slow, downloading the code from the UI never completed, and the author warns to push often because nothing stops OpenHands deleting files.
Published Mar 4, 2025self-described: Solo; built an ecommerce web app in the OpenHands web UI
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Rybens92 calls OpenHands the best alternative to proprietary coding agents and runs it on a US$10 or US$20 Chutes.ai subscription to avoid paying per token.
Published Aug 27, 2025self-described: Personal use on a Chutes.ai model subscription
Practitioner account, pseudonymous; opinion; not counted, takes no position
On their first run, OpenHands with Claude Sonnet 3.7 built a small WebGPU app with unit tests and served it for review for about US$0.44. Their attempt with a local model failed to start.
Published May 24, 2025self-described: First run, Claude Sonnet 3.7
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits
No opinion stated
ByteDance Seed research team, authors of Multi-SWE-bench
ByteDance adapted OpenHands to Java, TypeScript, JavaScript, Go, Rust, C, and C++ and ran it against Agentless and SWE-agent on 1,632 issues. OpenHands had the highest resolve rate in five of the seven languages, and its model-driven workflow took more turns and cost more than fixed-workflow Agentless.
"Overall, MopenHands outperforms the others in most cases, achieving the highest resolved rate in five out of seven languages, while MSWE-agent wins twice and MagentLess wins once."
Excerpt, ByteDance Seed
Published Apr 3, 2025self-described: Research team at ByteDance running an adapted OpenHands (MopenHands) on 1,632 issues in seven languages with nine models
In a company trial OpenHands failed to build an API layer after thirty minutes, but wrote internal READMEs and test coverage well; best for routine, well-defined tasks.
Published Jan 5, 2025self-described: Evaluated against typical development scenarios in their (unnamed) company environment
Checked Oct 12, 2026.Spending controls depend on where OpenHands runs. A maximum budget per conversation stops a conversation at its limit, and Cloud organizations add monthly budgets with alerts at 80, 90, and 100 percent. A report of unexpected spend does not establish that spending controls are missing. Organization budgets
4Security & accessAll 7 sources on it raise it as a concernWhat the agent can reach: mounted files, the Docker socket, credentials, and repository permissions.
With the GitHub resolver on claude-opus-4-5, the model opened its own pull request through the GitHub API with the token in its sandbox, and the resolver then opened a second one.
Published Feb 23, 2026self-described: OpenHands GitHub resolver with claude-opus-4-5
Practitioner account, pseudonymous; direct use; counts toward Reliability
A website prompt injection made OpenHands download and run malware joining a C2 server; the sandbox limits but does not remove exposure, and disclosure got slow vendor responses.
Published Aug 10, 2025self-described: Independent security testing; disclosed to All-Hands AI in March 2025, published after 140+ days
Practitioner account, self-described; structured test; counts toward Operational control
Shows a prompt injection that makes OpenHands render a Markdown image and leak the GITHUB_TOKEN from its container, bypassing the model's initial refusals.
Published Aug 9, 2025self-described: Independent security testing of the OpenHands agent
Practitioner account, self-described; structured test; counts toward Operational control
Running OpenHands offline with Devstral on a 24GB GPU, foobarg found the configuration broken and undocumented, objected to mounting the container socket, and saw Devstral fail almost every basic task.
Published May 24, 2025self-described: Fully offline setup: Devstral Q4_K_M on Ollama, OpenHands in podman
Finds OpenHands delightfully good with clear instructions and a free Gemini model, but self-hosting on Kubernetes took several attempts and needs a privileged pod with the Docker socket.
Published Feb 24, 2025self-described: Solo; ran OpenHands locally, then self-hosted it on their own Kubernetes cluster
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Runs OpenHands locally, has it write and run a Hacker News bash script that it debugs on its own; likes local open-source use but flags the freedom it gets on the machine.
"Pro uh M2 Chip I think um you can see runs locally Port 3000 and um it's got integration to vs code over here um and I just asked the the coder um the the AI agent to please write a bash script which displays…"
Running locally with a mounted folder, each new conversation creates an unwanted git repository and gives the folder and every agent-created file to group root, so morgaesis runs chown by hand.
Published Oct 1, 2025self-described: Local Docker install with a mounted project folder, OpenHands 0.57
Practitioner account, pseudonymous; direct use; counts toward Operational control
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.OpenHands' FAQ states that safety depends on the backend. The process sandbox runs with the host user's permissions, and broad mounts, privileged mode, host networking, or access to the Docker socket weaken container isolation. FAQs
5Dependence on the model7 of 8 sources on it raise it as a concernResults that rise or fall with the connected model, with weaker open-weight or local models failing on tool use.
Asked to add an HTML page, the agent failed every file edit with a missing-parameter error on claude-sonnet-4; switching to qwen3-coder-plus cleared it after one error.
Published Sep 4, 2025self-described: OpenHands 0.55
Practitioner account, pseudonymous; direct use; counts toward Reliability
The OpenHands CLI works well for tbiens with Devstral; Qwen3 Coder works 80 to 90% of the time but sometimes fails file edits with a malformed tool call.
Published Aug 1, 2025self-described: OpenHands CLI 0.50.0 with local models
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
Running OpenHands on local Devstral, simple prompts such as building a React button component usually fail: the model creates no files and tells the user to create them.
Published Jun 6, 2025self-described: Local Devstral, a new create-react-app repository
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Running OpenHands offline with Devstral on a 24GB GPU, foobarg found the configuration broken and undocumented, objected to mounting the container socket, and saw Devstral fail almost every basic task.
Published May 24, 2025self-described: Fully offline setup: Devstral Q4_K_M on Ollama, OpenHands in podman
With a 3090, says they have used "more or less every model I can fit onto the GPU" with Ollama for refactors, tests and documentation, and none was as good as Claude. OpenHands too was below par for simple tasks with local models, and absolutely terrible with GPT 4o.
Published Mar 5, 2025self-described: Ollama on an RTX 3090, plus Claude
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
Daniel Manzke, Medium (works on an enterprise search product)
Spent about US$200 in tokens building a prototype. Token use exploded late as files were regenerated and the codebase ballooned. Finds it great for prototyping and unready for complex products.
Published Mar 1, 2025self-described: Weekend prototype of a Q&A app against their company's enterprise search APIs
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Finds OpenHands delightfully good with clear instructions and a free Gemini model, but self-hosting on Kubernetes took several attempts and needs a privileged pod with the Docker socket.
Published Feb 24, 2025self-described: Solo; ran OpenHands locally, then self-hosted it on their own Kubernetes cluster
Practitioner account, self-described; ran the rollout; counts toward Delivered outcomes, Operational control, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.OpenHands' model guidance states that open-weight and local models still vary widely in tool-use reliability. When responses slow down or arrive as malformed JSON, it advises a stronger model, a larger context window, or a frontier model. LLM overview and model recommendations
Questions the sources split on, with the count on each side.
Evidence remains mixed
Should teams run OpenHands on frontier hosted models, or on open-weight models they serve themselves?
1116
Frontier hosted models, 11 sources
Some run OpenHands on Claude, GPT, or Gemini through a provider API for the strongest results.
Open-weight models, 16 sources
Others run it on open-weight models such as Devstral or Qwen, locally or on their own servers, for cost or control.
Evidence remains mixed
Should OpenHands work as a hands-off agent, or do engineers get more from an interactive tool for the same work?
54
Hands-off agent, 5 sources
Some hand OpenHands whole tasks and review the result.
Interactive tools, 4 sources
Others prefer tools they steer step by step, such as Aider, Cline, Claude Code, or an IDE agent.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 3 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
6 sources. These accounts focus on whether a team trial produced usable work, what made the agent finish its tasks, and the setup and cost a team has to own.
Individual builders
70 sources. These accounts focus on whether one conversation finishes, what it costs on the model the builder chose, and how OpenHands compares with tools they steer step by step.
All practitioners
76 sources. These accounts give the broadest read. They combine solo and team settings, which can reach different conclusions about OpenHands.
76 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders70 sources, counted here
Emphasizes Whether a conversation finishes and what it costs on the chosen model
Very small team2 to 10 engineers2 sources, counted here
Emphasizes Whether a trial on company work beats doing it by hand
Professional team11 to 50 engineers, or a named company's team1 sources, counted here
Emphasizes Setup scripts, repository rules, and CI around the agent
Technical leadershipLeaders setting adoption across teams3 sources, counted here
Emphasizes Where to self-host and which models to allow
Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Almost every public account comes from one person running OpenHands on their own machine or account, and they judge it on setup, on whether a run completes, and on the model bill. The six multi-person accounts include a benchmark study and three technical leaders who chose OpenHands for company work, and none of them measures a team rollout, so a team decision needs its own pilot.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 76 sources. Change group
91 sources for this group, 15 of them documentation
Developer communities & issue trackers55, 60% of 91 sources
Product documentation15, 16% of 91 sources
Engineering blogs & reviews13, 14% of 91 sources
Talks & videos8, 9% of 91 sources
Older evidence is retained when it still applies. Sources that depend on a changed version, runtime, or model stay in the history, marked Needs a recheck.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of OpenHands now casts no vote; it still counts toward its topics and is listed, and 20 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +6 to +11 and all practitioners from +9 to +15.
Each source record links to an English-language page dated 2025 or later and names its author and publication date.
The page shows a finding only when at least 5 sources from 3 different authors discuss it. A disagreement requires at least 2 sources on each side.
Counts accounts of OpenDevin, the project's name until 2024. Leaves 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.
Leaves out Sandboxed execution (2 sources) and Requires strong review (7 sources, 3 of which mention review without raising it). Also leaves out the statement that a strong model is needed (2 sources) and the questions on time saved and on delegation (4 sources each).
Checks every documentation page against OpenHands' current docs, including the move to the Software Agent SDK and Agent Canvas.
Oct 25, 2026: added Stability. Of the accounts already on file, 2 call OpenHands reliable on their local setup, and 3 report it works with occasional errors or is not ready for production.
Oct 25, 2026: added Needs close steering, also drawn from earlier accounts. Here, 2 report the agent looping or heading the wrong way until they stepped in. Also, 1 describes giving small corrections without concern.
Oct 25, 2026: added ByteDance's Multi-SWE-bench paper, an independent run of OpenHands in seven languages, and three October 2026 GitHub issues on OpenHands Cloud sessions and rootless Docker.
Method
A running review of what engineering teams report about OpenHands, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +14 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +14 Mixed; with one vote per author it read +9 Mixed. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +9 Mixed and now reads +15 Mixed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 3, individual builders 7 of 49, all practitioners 7 of 52.
Limits
GILD reviewed 76 English-language public sources dated 2025 or later. The record contains 23 Reddit posts and comments, 19 Hacker News comments, 13 GitHub issues from users outside the OpenHands team, 12 blogs and reviews, 8 videos, and 1 independent benchmark paper. GILD kept one GitHub issue per distinct problem and scores each as mixed, because a bug report shows a problem without passing a verdict on the product. Counts describe these sources and do not represent all OpenHands users.
OpenHands was called OpenDevin until 2024, moved its agent onto the Software Agent SDK in OpenHands 1.0 (December 16, 2025). It archived the old local web GUI on July 27, 2026, with Agent Canvas as its browser client. Sources record the version and model inconsistently. Each source shows what it states. Sources from before 2025, and 2025 accounts of installing the legacy Docker runtime, are marked Needs a recheck.
Every count, and the sources behind it
22 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Unpredictable task success. OpenHands' guidance rates bug fixes with reproduction steps, test additions, and changes that follow existing patterns as the best fit. It asks for large refactors and architectural changes to be split into phases. When to use OpenHands, checked Oct 12, 2026
Usage and cost. Spending controls depend on where OpenHands runs. A maximum budget per conversation stops a conversation at its limit, and Cloud organizations add monthly budgets with alerts at 80, 90, and 100 percent. A report of unexpected spend does not establish that spending controls are missing. Organization budgets, checked Oct 12, 2026
Setup & runtime friction. Since OpenHands 1.0 the agent runs in a Docker, process, or remote sandbox through the Agent Server. Agent Canvas installs with npm or a single Docker command, and accounts of the legacy Docker runtime describe the earlier setup. Sandbox overview, checked Oct 12, 2026
Dependence on the model. OpenHands' model guidance states that open-weight and local models still vary widely in tool-use reliability. When responses slow down or arrive as malformed JSON, it advises a stronger model, a larger context window, or a frontier model. LLM overview and model recommendations, checked Oct 12, 2026
Security & access. OpenHands' FAQ states that safety depends on the backend. The process sandbox runs with the host user's permissions, and broad mounts, privileged mode, host networking, or access to the Docker socket weaken container isolation. FAQs, checked Oct 12, 2026