Main
Use OpenHands as a baseline: start with its default runtime, then layer your own tools and policies for your repo.
Make runs reproducible: lock versions, prefer containers, and keep a clear boundary between agent state and project state.
For teams, define guardrails: what the agent can modify, which commands are allowed, and how reviews/approvals happen.
Source-backed notes
- README positions OpenHands as “AI-Driven Development” with a docs site link.
- Repository license indicates MIT for content outside the enterprise directory.
- Repo is active and widely adopted based on stars and frequent pushes.
FAQ
- Is it free and open source?: Core is MIT licensed; enterprise/ may carry different terms (see LICENSE).
- How do I run it quickly?: README suggests Docker-first usage; start with
docker compose up. - What should I add first?: Add repo-specific tooling (tests, linters) and a clear approval workflow.