Access
Install
pip install openhands-aidocker run -it --pull=always -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.58-nikolaik -v /var/run/docker.sock:/var/run/docker.sock -v ~/.openhands:/.openhands -p 3000:3000 --name openhands-app docker.all-hands.dev/all-hands-ai/openhands:0.58Showcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementationevidence →
End-to-end implementation by the agent — multi-file changes, task completion
Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversightevidence →
Keeping a human in the loop — approvals, checkpoints, interrupts
Intent to spec — stories about intent to spec in this arenaIntent to specevidence →
Stories about intent to spec in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Repo integration — stories about repo integration in this arenaRepo integrationevidence →
Stories about repo integration in this arena
Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gatesevidence →
Quality gates on changes — review flow, required checks, merge protection
Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelismevidence →
Running many jobs at once — concurrency, fleets, queueing
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 5 free · 1 paid · 1 enterprise · 43 not stated in evidence
Follow the green: where the map greys out is where OpenHands stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Scoped API keys · Versioning policy · Full data export · Have an agent automatically generate and run tests to validate its own code changes before proposing them · Go from a mockup or design to a working implementation without an engineering handoff · Add a context file describing my codebase conventions so agents generate more relevant plans and code · Query generated documentation for any public or private repository
Subscribe to events via webhooks
~5/10
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~4/10
Explore an interactive API reference with runnable examples
~3/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—–
Get AI-generated insights and suggestions from my data inside the product
✓7/10
Set up automations that run autonomously in the background
✓8/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation
End-to-end implementation by the agent — multi-file changes, task completion
End to end feature delivery
Have an agent automatically clone the repo, install dependencies, and configure its own working environment
~4/10
Interactive takeover
Have an agent safely execute code and install dependencies inside an isolated sandbox
~6/10
Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight
Keeping a human in the loop — approvals, checkpoints, interrupts
Approval controls
Model control
Intent to spec — stories about intent to spec in this arenaIntent to spec
Stories about intent to spec in this arena
Natural language task intake
Plan approval
Assign a coding task to an agent directly from an existing issue or ticket
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Repo integration — stories about repo integration in this arenaRepo integration
Stories about repo integration in this arena
Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates
Quality gates on changes — review flow, required checks, merge protection
Ci remediation
Diff review
Pr review automation
Readiness checks
Have security alerts automatically validated and remediated with an opened pull request
✓8/10
Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism
Running many jobs at once — concurrency, fleets, queueing
Concurrent execution
Deployment flexibility
Run an agent headlessly inside CI/CD pipelines and shell scripts
✓7/10
Sorted by importance (agentic first) (high → low) · 73/73 stories · click a row’s chevron for the rationale and evidence
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 4/10 | Cclaimed | |
Have an agent autonomously diagnose and fix a reported bug C End to end feature delivery | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | full | 8/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 7/10 | Cclaimed | |
Have failed CI workflows automatically diagnosed and fixed with a proposed pull request C Ci remediation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | full | 7/10 | Cclaimed | |
Connect a GitHub repository so an agent can access the code and open pull requests against it C Version control integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 3 | partial | 6/10 | Cclaimed | |
Have an agent safely execute code and install dependencies inside an isolated sandbox C Sandbox execution | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | partial | 6/10 | Cclaimed | |
Have every pull request automatically reviewed with AI-generated inline comments C Pr review automation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | partial | 6/10 | Cclaimed | |
Run many agent tasks concurrently to scale delivery throughput C Concurrent execution | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 3 | partial | 6/10 | Cclaimed | |
Assign a coding task to an agent directly from an existing issue or ticket C Ticket driven tasking | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | partial | 5/10 | Cclaimed | |
Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task C Natural language task intake | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | partial | 5/10 | Cclaimed | |
Have an agent implement a requested feature end-to-end, including writing tests C End to end feature delivery | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 3 | partial | 5/10 | Cclaimed | |
Connect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directly C Project management integration | product-manager | Repo integration — stories about repo integration in this arenaRepo integration | 3 | partial | 4/10 | Cclaimed | |
Review a diff of an agent's changes and approve it before it becomes a pull request C Diff review | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 3 | partial | 4/10 | Cclaimed | |
Set tiered autonomy levels controlling what an agent can do without manual confirmation C Approval controls | engineering-lead | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 3 | partial | 4/10 | Cclaimed | |
Watch what a running agent is doing in real time, including its current status C Visibility monitoring | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 3 | partial | 4/10 | Tprobed | |
Add a context file describing my codebase conventions so agents generate more relevant plans and code C Knowledge context | developer | Repo integration — stories about repo integration in this arenaRepo integration | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Review and approve an agent's implementation plan before any code changes are made C Plan approval | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 3 | none | untested | none yet | |
Bring my own LLM or API key so agents run on the model of my choice C Model flexibility | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | fullfree | 8/10 | Cclaimed | |
Configure an agent to auto-approve all its actions instead of confirming each one C Approval controls | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | full | 8/10 | Tprobed | |
Have incoming issues automatically triaged with severity suggested and routed to the right owner C Pr review automation | ai-native user | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | full | 8/10 | Cclaimed | |
Have security alerts automatically validated and remediated with an opened pull request C Security remediation | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | full | 8/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 8/10 | Cclaimed | |
Self-host agent infrastructure locally, in containers, or on my own VMs C Deployment flexibility | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | fullfree | 8/10 | Cclaimed | |
Use a managed cloud offering to run agents without operating my own backend infrastructure C Deployment flexibility | developer | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | fullpaid | 8/10 | Cclaimed | |
Run an agent headlessly inside CI/CD pipelines and shell scripts C Headless automation | developer | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | full | 7/10 | Tprobed | |
Trigger an agent from CI/CD pipelines to fix a broken build or failing test C Ci remediation | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | partial | 7/10 | Cclaimed | |
Configure an agent to automatically open a pull request when its task completes C Diff review | developer | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Get notified when an agent completes a task or needs my input C Visibility monitoring | developer | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | partial | 6/10 | Cclaimed | |
License an enterprise deployment with SSO and commercial support for organization-wide rollout G Enterprise licensing | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | partialenterprise | 6/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partialfree | 6/10 | Cclaimed | |
Tag an agent in a chat thread to discuss and delegate a bug or task C Chat integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 2 | partial | 6/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Send follow-up instructions to an active agent session to steer its work without restarting C Interactive takeover | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | partial | 5/10 | Tprobed | |
Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work C Interactive takeover | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | partial | 5/10 | Cclaimed | |
Grant an agent access to my repositories with a one-click install, without complex setup C Version control integration | developer | Repo integration — stories about repo integration in this arenaRepo integration | 2 | partial | 4/10 | Cclaimed | |
Have an agent automatically clone the repo, install dependencies, and configure its own working environment C Environment setup | developer | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | partial | 4/10 | Cclaimed | |
Approve a task's scope and contract before an agent is allowed to modify the repository C Plan approval | engineering-lead | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | none | 0/10 | ||
Create agent sessions on behalf of other users in my organization C Concurrent execution | engineering-lead | Scale parallelism — running many jobs at once — concurrency, fleets, queueingScale parallelism | 2 | none | 0/10 | ||
Go from a mockup or design to a working implementation without an engineering handoff C End to end feature delivery | product-manager | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | none | 0/10 | ||
Have each task prompt automatically routed to the most suitable underlying model C Model control | ai-native user | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 2 | none | 0/10 | ||
See and manage plan-based daily task and concurrency limits for agent workflows G Usage quotas | engineering-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Attach a marked-up screenshot or mockup to a task so the agent implements the correct visual change C Natural language task intake | developer | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Convert user feedback submissions into structured tasks with proposed scope C Natural language task intake | product-manager | Intent to spec — stories about intent to spec in this arenaIntent to spec | 2 | none | untested | none yet | |
Have an agent automatically generate and run tests to validate its own code changes before proposing them C End to end feature delivery | ai-native user | Autonomous implementation — end-to-end implementation by the agent — multi-file changes, task completionAutonomous implementation | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Run a readiness report that evaluates how ready my repository is for autonomous agents C Readiness checks | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 2 | none | untested | none yet | |
Switch away from automatic model selection to a specific model of my choice C Model control | engineering-lead | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 1 | partialfree | 5/10 | Cclaimed | |
Approve key agent decisions from my phone while agents continue working C Approval controls | product-manager | Human oversight — keeping a human in the loop — approvals, checkpoints, interruptsHuman oversight | 1 | partial | 4/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 | ||
Automatically fix failing agent-readiness criteria in my repository C Readiness checks | engineering-lead | Review quality gates — quality gates on changes — review flow, required checks, merge protectionReview quality gates | 1 | none | untested | none yet | |
Query generated documentation for any public or private repository C Knowledge context | developer | Repo integration — stories about repo integration in this arenaRepo integration | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 50 stories with headroom
What would move OpenHands’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
OpenHands is an AI coding agent, so the axis of consuming MCP servers as a client is applicable (unlike serving MCP, which would be na for an agent), but no evidence in the pack mentions MCP integration, configuration, or tool-plugging capability at all.
Intent to spec — stories about intent to spec in this arenaReview and approve an agent's implementation plan before any code changes are made
nonemoves PA Scoreimpact 30
Missing: any documentation of a plan-generation step, an approval/confirmation gate prior to code edits, or user testimony confirming such a workflow exists.
Repo integration — stories about repo integration in this arenaAdd a context file describing my codebase conventions so agents generate more relevant plans and code
nonemoves PA Scoreimpact 30
No evidence in this pack mentions a repo-level context/convention file (e.g., microagents, custom instructions, or similar) that developers can add to guide agent behavior; the pack only covers CLI usage, deployment, integrations, and pricing.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: explicit export/download feature, documented open data formats, statement on data portability upon leaving the platform.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses data usage for AI model training, opt-out policies, or any privacy commitments regarding training data; the pack only covers CLI usage, deployment options, and integrations.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Evidence shows OpenHands supports bringing your own LLM keys, SAML/SSO, and general API access, but nothing describes issuing scoped or least-privilege API credentials specifically for an agent's actions/tool access.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Evidence shows OpenHands exposes an OpenAPI spec and general 'API support for automation and scripting,' and docs reference a 'V1' with legacy V0 pages excluded, but there is no documented API versioning scheme or deprecation policy anywhere in the pack.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
partialq3/10moves API qualityimpact 21
Missing: interactive API explorer UI, runnable/try-it code examples, confirmation the openapi.json is rendered as browsable docs.
Showing the top 8 of 50 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 50 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
GitHub README29 stories
- Run the product headlessly / in CI for automation
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Have an agent implement a requested feature end-to-end, including writing tests
- Have an agent automatically clone the repo, install dependencies, and configure its own working environment
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Have an agent safely execute code and install dependencies inside an isolated sandbox
- Switch away from automatic model selection to a specific model of my choice
- Get notified when an agent completes a task or needs my input
- Assign a coding task to an agent directly from an existing issue or ticket
- Read the product's source under an open license
- Self-host the core product
- Bring my own LLM or API key so agents run on the model of my choice
- Tag an agent in a chat thread to discuss and delegate a bug or task
- Connect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directly
- Connect a GitHub repository so an agent can access the code and open pull requests against it
- Grant an agent access to my repositories with a one-click install, without complex setup
- Have failed CI workflows automatically diagnosed and fixed with a proposed pull request
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Configure an agent to automatically open a pull request when its task completes
- Have incoming issues automatically triaged with severity suggested and routed to the right owner
- Run many agent tasks concurrently to scale delivery throughput
- Self-host agent infrastructure locally, in containers, or on my own VMs
- Run an agent headlessly inside CI/CD pipelines and shell scripts
openhands.dev20 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent implement a requested feature end-to-end, including writing tests
- Approve key agent decisions from my phone while agents continue working
- Get notified when an agent completes a task or needs my input
- Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task
- Assign a coding task to an agent directly from an existing issue or ticket
- Tag an agent in a chat thread to discuss and delegate a bug or task
- Connect a GitHub repository so an agent can access the code and open pull requests against it
- Have failed CI workflows automatically diagnosed and fixed with a proposed pull request
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Configure an agent to automatically open a pull request when its task completes
- Review a diff of an agent's changes and approve it before it becomes a pull request
- Have incoming issues automatically triaged with severity suggested and routed to the right owner
- Have every pull request automatically reviewed with AI-generated inline comments
- Have security alerts automatically validated and remediated with an opened pull request
Usage docs18 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent implement a requested feature end-to-end, including writing tests
- Have an agent automatically clone the repo, install dependencies, and configure its own working environment
- Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the work
- Send follow-up instructions to an active agent session to steer its work without restarting
- Configure an agent to auto-approve all its actions instead of confirming each one
- Approve key agent decisions from my phone while agents continue working
- Set tiered autonomy levels controlling what an agent can do without manual confirmation
- Watch what a running agent is doing in real time, including its current status
- Get notified when an agent completes a task or needs my input
- Describe a feature or bug in plain language and have it automatically turned into a scoped implementation task
- Do everything through the API that I can do in the UI
- Review a diff of an agent's changes and approve it before it becomes a pull request
- Run an agent headlessly inside CI/CD pipelines and shell scripts
Pricing docs18 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Perform bulk operations across many items at once
- Approve key agent decisions from my phone while agents continue working
- Switch away from automatic model selection to a specific model of my choice
- Do everything through the API that I can do in the UI
- Read the product's source under an open license
- Self-host the core product
- License an enterprise deployment with SSO and commercial support for organization-wide rollout
- Bring my own LLM or API key so agents run on the model of my choice
- Grant an agent access to my repositories with a one-click install, without complex setup
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Run many agent tasks concurrently to scale delivery throughput
- Use a managed cloud offering to run agents without operating my own backend infrastructure
- Run an agent headlessly inside CI/CD pipelines and shell scripts
docs.openhands.dev10 stories
- Build against official SDKs
- Have an agent autonomously diagnose and fix a reported bug
- Have an agent safely execute code and install dependencies inside an isolated sandbox
- Self-host the core product
- License an enterprise deployment with SSO and commercial support for organization-wide rollout
- Grant an agent access to my repositories with a one-click install, without complex setup
- Trigger an agent from CI/CD pipelines to fix a broken build or failing test
- Run many agent tasks concurrently to scale delivery throughput
- Use a managed cloud offering to run agents without operating my own backend infrastructure
- Self-host agent infrastructure locally, in containers, or on my own VMs
OpenAPI spec5 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 17 testable claims verified · 0 contradicted → integrity 24/100
20 distinct capability claims found in OpenHands’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
13
Unverified
0
Contradicted
33
Undersold
Verified (4)
“Type natural language tasks and get instant feedback from the agent”
Operate the product with natural-language commandsfullproof ↗
“Auto-approve all agent actions instead of confirming each one”
Configure an agent to auto-approve all its actions instead of confirming each onefullproof ↗
“Composable Python SDK for building code-working agents”
“API support for automation and scripting”
Drive the product through a documented public APIfullproof ↗
Unverified (15)
“Resume previous conversations with the agent”
Take over an in-progress agent task in my editor, terminal, or browser to finish or redirect the workpartialproof ↗
“Works with any LLM you choose to bring”
Bring my own LLM or API key so agents run on the model of my choicefullproof ↗
“Create automations that integrate with Slack, GitHub, Linear, and more, triggered on a schedule or via webhook events”
“Create automations that integrate with Slack, GitHub, Linear, and more, triggered on a schedule or via webhook events”
“Run agents locally, in Docker, on VMs, or any self-hosted backend”
Self-host agent infrastructure locally, in containers, or on my own VMsfullproof ↗
“Managed cloud service to run OpenHands without operating your own backend/sandbox infrastructure”
Use a managed cloud offering to run agents without operating my own backend infrastructurefullproof ↗
“Enterprise offering with licensed self-hosting or managed deployment and commercial support”
License an enterprise deployment with SSO and commercial support for organization-wide rolloutpartialproof ↗
“Watches for bugs/incidents, gathers logs and recent changes, suggests severity, and routes issues to the right owner”
Have incoming issues automatically triaged with severity suggested and routed to the right ownerfullproof ↗
“Watches for a configurable PR label, inspects PR context, and posts an AI review comment once per label event”
Have every pull request automatically reviewed with AI-generated inline commentspartialproof ↗
“Detects failed workflows, inspects logs, identifies likely cause, and opens a PR with a proposed fix”
Have failed CI workflows automatically diagnosed and fixed with a proposed pull requestfullproof ↗
“Reviews security alerts, validates findings, updates affected code, and opens a remediation PR”
Have security alerts automatically validated and remediated with an opened pull requestfullproof ↗
“Watches Slack channels for @openhands mentions, opens a conversation with message context, and replies when done”
Tag an agent in a chat thread to discuss and delegate a bug or taskpartialproof ↗
“Hosted cloud access from desktop and mobile devices”
Approve key agent decisions from my phone while agents continue workingpartialproof ↗
“Enterprise SAML / SSO support”
License an enterprise deployment with SSO and commercial support for organization-wide rolloutpartialproof ↗
“Open Source and Cloud plans let users bring their own LLM keys”
Bring my own LLM or API key so agents run on the model of my choicefullproof ↗
Undersold (33)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventsfullproof ↗
Have an agent autonomously diagnose and fix a reported bugfullproof ↗
Have an agent implement a requested feature end-to-end, including writing testspartialproof ↗
Have an agent automatically clone the repo, install dependencies, and configure its own working environmentpartialproof ↗
Send follow-up instructions to an active agent session to steer its work without restartingpartialproof ↗
Have an agent safely execute code and install dependencies inside an isolated sandboxpartialproof ↗
Set tiered autonomy levels controlling what an agent can do without manual confirmationpartialproof ↗
Switch away from automatic model selection to a specific model of my choicepartialproof ↗
Watch what a running agent is doing in real time, including its current statuspartialproof ↗
Get notified when an agent completes a task or needs my inputpartialproof ↗
Describe a feature or bug in plain language and have it automatically turned into a scoped implementation taskpartialproof ↗
Assign a coding task to an agent directly from an existing issue or ticketpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Read the product's source under an open licensepartialproof ↗
Connect issue trackers like Jira, Linear, ClickUp, or Monday.com so agents can manage tickets directlypartialproof ↗
Connect a GitHub repository so an agent can access the code and open pull requests against itpartialproof ↗
Grant an agent access to my repositories with a one-click install, without complex setuppartialproof ↗
Trigger an agent from CI/CD pipelines to fix a broken build or failing testpartialproof ↗
Configure an agent to automatically open a pull request when its task completespartialproof ↗
Review a diff of an agent's changes and approve it before it becomes a pull requestpartialproof ↗
Run many agent tasks concurrently to scale delivery throughputpartialproof ↗
Run an agent headlessly inside CI/CD pipelines and shell scriptsfullproof ↗
Claims outside our story set (2)
Real capability claims found in OpenHands’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Switch between local, remote, and cloud agents without losing context”
source ↗“Run OpenHands, Claude Code, Codex, Gemini, or any ACP-compatible agent across local, remote, and cloud backends”
source ↗
Business model
Self-hostable open-source runtime (Apache-2.0) is free; the hosted OpenHands Cloud is usage-based with free starter credits.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% · openapi.json 100% (30d, checked every 6h since Sep 8 '26)
