# OpenHands

Open-source AI software development agent for coding tasks, repositories, and developer workflows.

## Summary
OpenHands is an open-source AI-driven development project for letting agents work on software tasks, inspect repositories, modify code, and support developer workflows.


## Guide
OpenHands is a practical open-source reference point for the coding-agent category. It is not just a chat interface for code explanations; it is aimed at agents that work inside software development workflows.

### What it is
OpenHands is an open agent resource to evaluate by action surface: what software it can operate, which tools or browser steps it touches, and how much supervision it needs before it can run real work.

### Why it matters
Coding agents need more trust than chatbots because they can change files, run commands, and touch repositories. OpenHands is useful because its implementation can be inspected, tested, and compared against closed coding-agent products.

### How it works
Start with one safe workflow for OpenHands. Inspect official setup instructions, required credentials, execution logs, approval points, and failure recovery before expanding from a sandbox task into production automation.


## Use Cases
- Open coding-agent benchmarking: Use OpenHands to test repository-level tasks and compare results with other coding agents.
- Developer workflow automation: Evaluate whether repeated code maintenance tasks can be delegated safely under review.
- Agent safety and sandboxing studies: Study the operational boundaries needed when agents can modify code and run commands.

## Alternatives
- Use browser-use or OpenClaw for web actions vs browser agents: OpenHands is for software development workflows. Browser-oriented agents are better when the core task happens inside websites.

### Getting Started
- Read the docs: https://docs.openhands.dev/
- Review the repository: https://github.com/OpenHands/OpenHands

### FAQ
- What should I check before using OpenHands?
  - Start with one safe workflow for OpenHands. Inspect official setup instructions, required credentials, execution logs, approval points, and failure recovery before expanding from a sandbox task into production automation.
- Is OpenHands open source?
  - OpenHands is listed with MIT based on the official source links in this profile. Re-check the repository, model card, or docs before production use.
- Who should evaluate OpenHands?
  - OpenHands is most worth evaluating for developers evaluating open-source coding agents.
- Is OpenHands only for developers?
  - Yes, its clearest fit is software development and repository workflows.
- Should I use OpenHands on production code immediately?
  - No. Start with a sandbox repository and review every change before moving to important code.
## Why It Matters
OpenHands matters because coding agents are moving from chat suggestions toward repository-level action. It gives developers an open implementation to inspect when evaluating how agents plan, edit, test, and recover inside real codebases.


## Best For
- Developers evaluating open-source coding agents
- Teams that want an inspectable alternative to closed coding-agent products
- Researchers studying repository-level task automation and software engineering agents

## Not For
- Non-technical users looking for a general personal assistant
- Teams unwilling to review sandboxing and repository permissions before using coding agents

## What It Actually Does
- Repository-level coding agent: OpenHands is designed around software development tasks, not only answering programming questions.
  - Why it matters: Real coding assistance requires file edits, terminal work, testing, and iteration.
- Open implementation for agent workflows: The public repository lets builders inspect how the system approaches planning, execution, and developer controls.
  - Why it matters: Coding agents touch valuable codebases, so inspectability matters.
- Strong fit for coding-agent comparison: OpenHands is a useful reference point when comparing open coding agents against proprietary tools.
  - Why it matters: Teams can evaluate tradeoffs around local control, hosted convenience, and engineering safety.

## Typical Use Cases
- Issue triage and code changes: Use OpenHands as a candidate when an agent needs to inspect a repository and propose implementation changes.
- Coding-agent research: Study how an open coding agent handles tasks, tools, sandboxing, and developer feedback.
- Self-hosted developer automation: Evaluate whether parts of your coding workflow can run in an inspectable open-source environment.

## How It Compares
- Choose OpenHands for software development workflows vs browser automation agents: browser-use and OpenClaw are stronger for web workflows. OpenHands is more directly focused on repositories, code tasks, and software engineering.

## Command Line
### Clone the OpenHands repository
Start with the official repository and follow the docs for the current Docker or runtime setup.

```bash
git clone https://github.com/OpenHands/OpenHands.git
```

## Facts
- Category: agents
- Resource type: agent
- Open source: yes
- License: MIT
- Last verified: 2026-04-19
- GitHub repo: OpenHands/OpenHands
- GitHub stars: 71464

## Capabilities
- workflow-orchestration
- tool-calling

## Structured Use Case Tags
- self-hosted-ai
- developer-workflow

## Getting Started
- Open the GitHub repository: https://github.com/OpenHands/OpenHands
- Read the docs: https://docs.openhands.dev/
- Visit the project website: https://openhands.dev

## Links
- GitHub: https://github.com/OpenHands/OpenHands
- Homepage: https://openhands.dev
- Docs: https://docs.openhands.dev/

## Structured Outputs
- JSON: https://www.openagent.bot/agents/openhands.json
- Markdown: https://www.openagent.bot/agents/openhands.md
- Canonical: https://www.openagent.bot/agents/openhands