← Back to all projects
OpenHands
Autonomous software engineer running in a sandboxed container
OfficialMIT
What is OpenHands?
Edits files, runs tests and browses documentation inside an isolated container, so a failed run cannot damage the host. Competitive on SWE-bench style benchmarks, but budget carefully before pointing it at a real repository — long autonomous runs consume a great deal of tokens and still need review before anything is merged.
What can you do with OpenHands?
- Run the whole stack locally —
npm install -g @openhands/agent-canvasinstalls the launcher, and theagent-canvascommand starts the full local stack by default at localhost:8000, with--frontend-onlyand--backend-onlyto run the pieces separately. - Sandbox the agent in Docker — Running
ghcr.io/openhands/agent-canvaswith-v ${PROJECTS_PATH}:/projectsgives the agent access to any project underPROJECTS_PATH, while the npm and from-source launchers carry the README's warning that the agent server has full access to your filesystem. - Switch between agent backends — Agent Canvas talks to OpenHands Agent Servers over REST, one per host/port, so a shared server doing code review and dependency updates and a laptop-local agent sit in the same frontend and are added from the UI.
- Use agents other than OpenHands — Claude Code, Codex, Gemini or any Agent-Client Protocol (ACP) agent runs in the same canvas, and the LLM behind them is yours to choose.
- Automate recurring engineering chores — Paired with the Automation Server, agents run on a schedule or on webhook events — decomposing GitHub issues into tasks, or publishing generated reports to Slack — with integrations for Slack, GitHub, Linear and Notion.
Star history
15 Aug to 30 Oct · +8.1k
84.1k92.3k
Frequently asked questions
Is OpenHands free for commercial use?
OpenHands is released under the MIT licence — OSI-approved open source, which permits commercial use.
How can OpenHands be deployed?
OpenHands is available as Self-hosted / Runs locally / Managed cloud.