Agent platform

OpenHands

Agent platform with selectable local, sandboxed, and remote runtimes.

Status
Active
License
MIT core; separate enterprise terms
Evidence
Documented + code-verifiable, 23 sources
Product record checked
2026-07-27

At a glance

An open agent platform and developer control center with CLI, web, SDK, and automation surfaces; provider and local-model flexibility; MCP and browser tools; and local, Docker, or remote execution environments.

Good choice if

  • Longer autonomous tasks in an isolated runtime
  • Self-hosted agent-platform and SDK workflows
  • Issue, IDE, and automation integrations beyond one terminal session

Check before choosing

  • The platform is materially heavier than a focused CLI and spans separately versioned OSS app, Cloud, and SDK release trains
  • Docker is the recommended local isolation; ProcessSandbox runs directly on the host and is explicitly unsafe for untrusted tasks
  • Headless CLI runs in always-approve mode, and direct SDK execute_tool calls bypass the normal security analyzer and confirmation policy
See 4 more considerations
  • Security analyzers and confirmation policies reduce risk but do not make model-generated actions trustworthy; remote deployments still require infrastructure hardening
  • Persistent memory is opt-in, while session persistence, condensation, and memory solve different context problems
  • Scheduled and event-driven automations run unattended in fresh sandboxes with the user's configured LLM, stored secrets, MCP integrations, and Git-provider credentials, so trigger scope and credential scope still require review
  • Local models are supported with documented functional limitations, and the project evaluation harness is not independent evidence of product quality

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationSandbox availableDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible + browserDocumented mechanism, not a performance score.
  • Context & statePersistent stateDocumented mechanism, not a performance score.
  • Lifecycle & recoverySession resumeDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsPolicy controlsDocumented mechanism, not a performance score.

Public code audit

3/5public artifacts present
Security policy
Not found
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The OSS 1.11.0 application tree contains 589 test-like files, 26 workflows, and contributor documentation but no root security policy or dedicated evaluation suite. Cloud and SDK follow separate release trains, and split-licensed or hosted components are outside this root-repository audit.

Inspect commit 11ca68ab2e15dcd85c21e4d7d3409e7a259369ac, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control
DocumentedBuilt-in or product-supported browser controlSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Isolated execution
DocumentedDocumented execution-isolation mechanismSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Primary evidence

Each capability claim is tied to a first-party record and a verification date.

Product record checked 2026-07-27
View 15 additional sources
Product and interfaces4 sources
Execution and control1 sources
Agents, state and recovery2 sources
Automation and extensions4 sources
Enterprise and operations2 sources
Releases and public code audit2 sources