Head to head · Agent harnesses · October 2026 research run

OpenHands vs Verdent

OpenHands scores 70.3 (BB) on agent readiness against Verdent's 39.7 (E), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Which one, for what

OpenHands BB

Best for Teams that want to self-host a coding agent with a web UI, per-conversation Docker sandboxes and scheduled or webhook automations, or embed the agent through a Python SDK and REST API.

Ahead on

  • Reliability, 90 against 43
  • Schema & documentation, 90 against 55
  • Agent ergonomics, 78 against 35
  • Security & auth, 64 against 33
  • Payments & pricing, 60 against 20
  • Maintenance & community, 85 against 61
  • Transparency & trust, 67 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Confirmation mode is off by default in Agent Canvas, and the npm install gives the agent the host's whole filesystem

Verdent E

Best for A person who wants a desktop app to plan and run several coding tasks at once, possibly on their own Claude Code or Codex.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No CLI, print mode, API or SDK, so a pipeline can't start or read a run except through a paired chat bot

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability OpenHands +47

OpenHands 90

Read as a local package. Official npm package @openhands/agent-canvas (Node 24 or later, plus uv), a Docker image on GHCR and openhands-sdk on PyPI (Python 3.12 or later) (20). A CI workflow (ci.yml) runs on main beside desktop, Docker and end-to-end workflows; the runs passed on every load on 1 October, and GitHub's pages refused us on 1 November, so the award rests on that check (25). 456 open issues and 395 open pull requests with priority labels and a high-priority Cloud resume bug (#17664), per the 1 October check, not re-read on 1 November (18). Dated release notes for every Canvas version and a written SDK rule of at least five minor releases before a public API or REST contract is removed, which the SDK followed on 28 October when it dropped the ACP curated model lists at their stated 1.59.0 deadline, but the Canvas CHANGELOG.md still stops at 1.0.0-alpha.2 (12). Canvas is 1.34.0 and the SDK 1.59.0, and the README's beta badge was removed on 23 October 2026 (commit 4d1c4d1, noted in the 1.33.0 release notes), so the product is no longer labelled beta. Only the Apps extension API keeps a beta label (15).

Verdent 43

Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.

Agent ergonomics OpenHands +43

OpenHands 78

Harness reading of the framework line, scored on what an agent or pipeline driving it has to supply. The default agent carries three tools (terminal, file editor, task tracker), and filter_tools_regex trims MCP tools before they reach the model (23). Stuck detection is on by default and a condenser compacts long histories, but Canvas leaves max_iterations unset and we found no cost cap (15). Headless runs go through the SDK, the Agent Server REST API or the Cloud API with typed events, and the old CLI's --headless mode is unmaintained (14). Conversations persist and resume, and a Docker conversation keeps its workspace and history when the container is replaced (16). Python SDK and TypeScript client, but the quickstart needs Node 24 and uv, and the defaults skip both confirmation and the sandbox (10).

Verdent 35

Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.

Payments & pricing OpenHands +40

OpenHands 60

No payment protocol (0). Scored on the paid options and the OpenHands LLM provider. The docs publish per-token prices for the OpenHands LLM provider at provider rates with no markup, and the pricing page now lists Agent Canvas free, Teams at $500 a month for up to 10 users (plus $50 a seat, 30-day trial) and Enterprise by sales (20). The MIT stack is free to self-host, and two DeepSeek models are free on app.all-hands.dev (20). It runs any model through LiteLLM, local ones included, so an agent can install and run it with no signup (20). The provider price table still lists 2025 models, so it may be stale.

Verdent 20

Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.

Schema & documentation OpenHands +35

OpenHands 90

The Agent Server REST API has an OpenAPI 3.1 spec in the docs repository (40 paths, still labelled 0.1.0), the Cloud API has another (155 paths), SDK models are Pydantic-typed and there's a TypeScript client (25). llms.txt at docs.openhands.dev (551 lines on 1 November), with no CLI, local GUI or V0 pages in it (10). The docs have a when-to-use page and examples of good and bad task instructions. On 23 October the Deprecated Projects group (local GUI, CLI, V0) was taken out of the navigation and links to it reworded towards Agent Canvas, though the pages stay reachable by URL and the SDK architecture page still links the CLI repository (15). Confirmation policies, security analysers and MCP configs are discriminated Pydantic unions with validators (13). SDK examples are checked by a CI workflow and there are troubleshooting pages, but we found no error reference for the Agent Server (12). Dated release notes for each Canvas version in the docs (1.25.0 to 1.34.0 added since 1 October), and release tags (15).

Verdent 55

Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as "certain tool executions" and "destructive operations" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.

Security & auth OpenHands +31

OpenHands 64

Harness reading of the framework checklist, as for goose and the other agent harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Agent Canvas still sends a canvas_install event to PostHog through z.openhands.dev on first use "regardless of consent" (telemetry.ts header, re-read on 1 November), and the consent banner's box is still defaultChecked. AGENT_CANVAS_DISABLE_TELEMETRY=1, --disable-telemetry, VITE_DO_NOT_TRACK=1 or the browser's Do Not Track setting stops all of it, the last since 1.26.0 (15). Confirmation policies (always, never, at or above a risk level) and a Docker sandbox per conversation exist, but Canvas still starts with confirmation_mode: false and the npm install runs on the host with full filesystem access. No network egress controls found. Local listeners bind to 127.0.0.1 with an injected session key, and since SDK 1.52.0 (5 October) DockerWorkspace publishes its ports on loopback (12). LLM, Invariant and GraySwan risk analysers and a policy-rail module, documented, all advisory (11). Conversation event logs, completion logs and OpenTelemetry tracing through Laminar, with hosted Laminar setup documented on 16 October (13). Security programme. openhands.dev's security.txt expired on 28 October 2026 (re-read on 1 November), though the responsible-disclosure policy it names still loads. A Vanta-hosted trust page per the 1 October check, and the git diff injection published as an OpenHands advisory with a CVE. CVE-2026-112346, the SDK's unauthenticated sandbox server, was published by VulnCheck on 26 October with no OpenHands advisory found. No bug bounty found. 13, down from 15 for the expired file, read as shopware's and tokeneconomizer's expired files are (still credited for the policy behind them, less than a valid file).

Verdent 33

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.

Maintenance & community OpenHands +24

OpenHands 85

Agent Canvas 1.34.0 on 2026-10-27 and SDK 1.59.0 on 2026-10-28, by the repository tags (30). 29 Canvas releases (1.9.0 on 3 August to 1.34.0) and 33 SDK releases (1.40.1 on 5 August to 1.59.0) in the 90 days from 3 August, not counting the security rebuild tags (20). Issues labelled by priority, but 456 open issues and 395 open pull requests and no visible reply times per the 1 October check; GitHub's pages refused us on 1 November (16). npm, PyPI and GHCR packages current per the 1 October check (the registries didn't answer from our shell on 1 November). The unmaintained openhands CLI is gone from the docs navigation and the pricing page but its pages remain (10). CI on main, Dependabot, a security scan and an API-breakage check on the SDK, and security rebuilds of older images (agent-canvas 1.23.0-r3, agent-server 1.49.5-r3, 29 October) (9).

Verdent 61

Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.

Score by category

CategoryWeight this runOpenHandsVerdentEdge
Reliability16%209043OpenHands +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29055OpenHands +35
Agent ergonomics13%16.27835OpenHands +43
Security & auth14%17.56433OpenHands +31
Payments & pricing10%12.56020OpenHands +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88561OpenHands +24
Transparency & trust7%8.86755OpenHands +12
Negative events≤15-7-2
TotalBB 70.3/100E 39.7/100

Facts side by side

FactOpenHandsVerdent
KindAgent harnessAgent harness
VendorAll Hands AIVerdent AI, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted serviceProprietary. The terms of use from Verdent AI, Inc. forbid reverse engineering or copying any component, and no source is published
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-282026-10-29
Terms last updatedno document linked2026-05-25
Privacy policy last updated2025-09-032026-05-26
Customer content may train modelsyesyes
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity90k starsnone
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

OpenHands

A self-hosted coding agent with a typed SDK, an Agent Server API and a Docker container per conversation on request. Agent Canvas still starts with confirmation off on the host's filesystem, sends an install event before asking consent, and a critical SDK sandbox flaw fixed in October was published by a third party.

Verdent

A desktop and editor coding agent that splits a goal into parallel workers in git worktrees, with a read-only Plan Mode, MCP servers and the option to run workers on Claude Code or Codex. It has no CLI, API or sandbox, sends context through Verdent's servers, and has had no free tier since 29 October 2026.

Before you call either

OpenHands

  1. Set AGENT_CANVAS_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 before the first start
  2. Start Canvas with OH_CONVERSATION_RUNTIME=docker or use the Docker image. The npm install runs the agent on the host
  3. Turn on confirmation mode with a risk threshold. Canvas starts with it off
  4. Pin openhands-sdk and openhands-workspace at 1.52.0 or later so DockerWorkspace binds to loopback, and set OH_SESSION_API_KEYS_0 on any reachable Agent Server
  5. Use the SDK or the Agent Server API for headless runs. The openhands --headless CLI is no longer maintained

Verdent

  1. Don't plan to drive Verdent headless. Hand the task to the person using the desktop app, or use a harness with a print mode
  2. Start large changes in Plan Mode and review plan.md before switching to Agent Mode
  3. Add MCP servers in the project's .mcp.json or ~/.verdent/mcp.json in the mcpServers shape
  4. Keep work under git, since rollback relies on git and there is no sandbox
  5. Budget in credits at about $0.059 each, because there is no free allowance since 29 October 2026

Questions

Which is better for AI agents, OpenHands or Verdent?

OpenHands scores 70.3 (BB) on agent readiness against Verdent's 39.7 (E), and leads in every scored category.

Are OpenHands and Verdent open source?

OpenHands is open source (MIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted service). No open-source release is listed for Verdent.

Other comparisons with OpenHands or Verdent

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.