OpenHands

Plan

1. SupportsWork planning: Supports

   Work planning, supports. The Jira integration reads a labeled ticket, writes a plan, and implements it, and automation templates triage new Linear issues and Jira incidents. The ticket system stays the planning record.

Build

1. Codebase context: Supports

   Codebase context, supports. Repository skills and AGENTS.md load project context into every conversation. Enterprise adds a Large Codebase SDK, while code search across the organization stays with a dedicated tool.

2. OpenHandsCoreCoding: Core

   Coding, core. This is OpenHands' primary role. The agent plans, edits, and runs code for a task on the model you configure, then opens a pull request for human review.

3. Agent runtime: Core

   Agent runtime, core. Agent Canvas and the CLI connect to an Agent Server, as do IDE integrations over the Agent Client Protocol. The server runs in Docker, process, Kubernetes, or managed Cloud sandboxes. Canvas also controls Claude Code, Codex, and Gemini CLI.

4. Tool execution: Core

   Tool execution, core. OpenHands runs commands and edits files inside its sandbox, with browser and MCP access. Work starts through GitHub, GitLab, Bitbucket, Slack, Jira, the Cloud API, or scheduled and event-driven automations.

Validate

1. Debugging: Supports

   Debugging, supports. The incident triage use case pulls Datadog errors and logs into a root-cause report and a proposed fix, while alerting and on-call stay in the monitoring stack.

2. Testing: Supports

   Testing, supports. OpenHands writes and runs tests. Stop hooks block completion until repository checks pass, and the QA workflow exercises the changed software as a user. Your team owns the test suite and CI.

3. Code review: Supports

   Code review, supports. A pull request review workflow and automation post review comments on a label or reviewer request, and merge approval stays with the engineering team.

4. Application security: Supports

   Application security, supports. The vulnerability remediation use case takes scanner findings, updates the affected dependencies or code, and opens fix pull requests. OpenHands is not the security system of record.

Ship

1. TouchesSource control: Touches

   Source control, touches. OpenHands pushes branches and opens pull requests on GitHub, GitLab, and Bitbucket. Enterprise adds Azure Repos and Bitbucket Data Center. The hosts remain the source-control system.

2. CI/CD: Touches

   CI/CD, touches. The agent runs inside GitHub Actions workflows and can open pull requests that fix failed checks, while build and deployment pipelines stay in your CI/CD platform.

Operate

1. Observability: Touches

   Observability, touches. Datadog errors can start an investigation and Enterprise analytics trace agent runs, but OpenHands does not monitor or alert on production services.