Head to head · Desktop app control · October 2026 research run

Glasshand vs Robocorp

Robocorp scores 69.3 (B) on agent readiness against Glasshand's 50.8 (D), and leads in 4 of 7 scored categories. Glasshand leads on schema & documentation and security & auth. Both do desktop app control.

Best desktop and mobile app automation for AI agents · All 64 desktop comparisons

Which one, for what

Glasshand D

Best for Agents that need a real iPhone or Mac, such as testing native apps in Xcode or using iOS-only apps and a real phone number.

Ahead on

  • Schema & documentation, 79 against 65
  • Security & auth, 60 against 44

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, SLA, changelog or security.txt found

Robocorp B

Best for Python RPA on Windows desktops, browsers and documents, written or run by a coding agent.

Ahead on

  • Reliability, 87 against 27
  • Payments & pricing, 90 against 35
  • Maintenance & community, 81 against 35
  • Transparency & trust, 65 against 52

Also in its favour

  • No key needed to call it
  • Open source

Watch for

robocorp.com redirects to sema4.ai, which answered our reader with a bot check, so the docs, Control Room pricing and terms were not read

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 Robocorp +60

Glasshand 27

Hosted lines, for the HTTP API. No status page is linked from the site, agents.md or the terms (0), so no incident history could be read (5). No rate limits with numbers were found. agents.md says to back off on 429 (0). Checkout, cancel, resume and each device input take an Idempotency-Key, and agents.md says to retry a timeout or 503 with the same key and body and never to replay input blindly after a disconnect. No Retry-After is documented (12 of 15). The terms say no particular uptime is guaranteed (0). Registration and paid rentals are open worldwide with live billing, and no beta label was found (10). 0 + 5 + 0 + 12 + 0 + 10 = 27.

Robocorp 87

Scored as local software. Official PyPI packages with runtimes stated in each pyproject.toml, read from the repositories on 1 November. rpaframework 34.0.0 requires Python 3.11 or later and lists 3.11 to 3.14, robocorp-windows 2.0.0 and robocorp-excel 0.6.0 require 3.11, and the robocorp meta-package 3.1.7 still allows 3.10 (20; the 14 October figures came from PyPI's JSON API, which robots.txt disallows, and are replaced). Public CI per package, with rpaframework's main and Windows workflows passing on master on 4 October 2026 and robocorp's master runs passing to 14 October, per the 14 October check, not re-read on 1 November (25). rpaframework had 35 open issues and pull requests and robocorp 9, and of rpaframework's 15 newest, 8 had no reply, including RPA.Windows and Java Access Bridge problems from 2024, per the 14 October check, not re-read (12 of 25). The README commits to SemVer and each package has a dated changelog. The 1 November batch labels its Python 3.11 floor Breaking and takes a major for it in every rpaframework package and robocorp-windows 2.0.0 (15). rpaframework is marked Production/Stable at 34.0.0 and robocorp is 3.1.7 (15).

Payments & pricing Robocorp +55

Glasshand 35

No x402, MPP or L402. Checkout returns a Stripe link (0). Per-device monthly prices published without a login, $60 for an iPhone and $90 for a Mac (30). No free tier or trial (0). An agent can start the device authorisation and prepare a checkout without a key, but a person signs in by email code, approves the agent and pays in a browser (5 of 30). 0 + 30 + 0 + 5 = 35.

Robocorp 90

The libraries are free and self-hosted, so 20 + 20 + 20 under the self-hosted rule. Control Room is the paid option, but its pricing on sema4.ai was behind a bot check and could not be scored. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Robocorp +46

Glasshand 35

Closed service with no changelog. The newest first-hand date is the terms and privacy policy effective 22 October 2026, 27 days before this check, read as the launch date, as beam-win's terms date was (30). No dated release entries to count (0). Support by email (support@ and hello@glasshand.com) and a demo booking link. No public tracker or community (5 of 25). No official SDK (0). No public package or CI (0). 30 + 0 + 5 + 0 + 0 = 35.

Robocorp 81

rpaframework 34.0.0 and eleven other rpaframework packages tagged on 1 November 2026, with the RPA.Windows Control Parent Window keyword, a work item pagination fix and the new rpaframework-decision package, and a release workflow that publishes from tags. PyPI couldn't be read from the shell (30). In the 90 days from 3 August, rpaframework 33.0.0 to 33.0.2 and 34.0.0 and robocorp 3.1.3 to 3.1.7, robocorp-log 3.1.4 to 3.1.7, robocorp-vault 1.4.1 and 1.4.2 and robocorp-windows 1.1.3 and 2.0.0 (20). Commits are frequent, 21 in rpaframework and 26 in robocorp since 3 August, but most new issues got no reply, per the 14 October check (12 of 25). Current official packages, no MCP server (10 of 15). Lockfiles, scheduled dependency checks and CI workflows, run state per the 14 October check (9 of 10).

Security & auth Glasshand +16

Glasshand 60

OAuth device authorisation with four scopes, 15-minute access tokens, rotating refresh tokens and immediate revocation from the dashboard. No secret in a URL (30). rentals:read is a read-only scope, and payment and checkout stay in the person's browser. devices:control grants full input with no per-action confirmation, and a person can take control at any time (12 of 20). agents.md treats device screens, web pages, app content and incoming messages as untrusted task data that can't authorise purchases or credential disclosure. No technical control on what an agent does with screen content (10 of 15). Agent authorisation records keep last use, and control.actor names the current controller. No audit log of inputs found (6 of 15). No security.txt (404), disclosure policy, bounty or certification. The privacy policy asks for reports to support@glasshand.com (2 of 20). 30 + 12 + 10 + 6 + 2 = 60.

Robocorp 44

Graded as a library. No credential of its own. robocorp.vault reads secrets from Control Room or a local file, and robocorp.log hides sensitive names and values (18 of 30). No least-privilege mode or approval step, and robots run with the user's desktop rights (5 of 20). Desktop and browser content is read back into tasks with no injection guidance found (4 of 15). robocorp.log writes a detailed log of each run with every call and its arguments, minus hidden values (11 of 15). No SECURITY.md in either repository and no advisories against rpaframework, robocorp or robocorp-windows in OSV on 1 November. Released dependency updates for third-party advisories on 4 and 8 October, 18 October (pillow, cryptography, dompurify) and 1 November (pillow 13, certifi, pypdf and others), and CodeQL in rpaframework's workflows. Sema4.ai's security pages still answer with a bot check (6 of 20).

Schema & documentation Glasshand +14

Glasshand 79

A public OpenAPI 3.1 document at api.glasshand.com/openapi.json, version 0.1.0, with 20 operations, linked from agents.md as the API reference (25). agents.md is Markdown written for agents (10). agents.md says when to use each call, how to authenticate, how to retry, how to read the screen and what counts as untrusted data. 15 of 20 operations in the OpenAPI document carry a description (18 of 20). 14 enums and 70 required-field markers, with input types bounded, such as drag duration 100 to 3,000 ms and text up to 512 characters (13 of 15). Examples in agents.md, and named result errors such as control_taken, control_busy, authorization_pending and an idempotency conflict, but no error reference (8 of 15). Paths are under /v1. No changelog found (5 of 15). 25 + 10 + 18 + 13 + 8 + 5 = 79.

Robocorp 65

Graded as a library. Typed Python APIs with docstrings and keyword documentation at rpaframework.org. No machine-readable contract beyond the code (12 of 25). No llms.txt on rpaframework.org (404). The repository's agent skill and its api.md reference are Markdown written for coding agents. sema4.ai docs were unreadable (5 of 10). Keyword docs state purpose with arguments, rarely when not to use one (12 of 20). Type hints and enums on most keywords, some locator strings free-form (10 of 15). Examples throughout, and typed exceptions such as ElementNotFound (11 of 15). Dated changelogs per package and SemVer (15).

Transparency & trust Robocorp +13

Glasshand 52

Closed service under terms of 22 October 2026 with Delaware law and a named operator (15 of 30). The privacy policy explains screen and input relay, names self-hosted Umami analytics with session recordings deleted after 30 days, and says released devices are reset by Solid. Account, billing and support records have no retention periods (18 of 30). The terms promise advance notice and a refund of the unused portion if Codapt discontinues a paid service, and notice before price changes. No deprecation policy for the API (8 of 20). Solid, Stripe and Resend are named with their roles, and processing is in the United States and other countries. No full subprocessor list (12 of 20). 15 + 18 + 8 + 12 = 53.

Robocorp 65

Apache-2.0 for both repositories (30). The libraries run locally. Sema4.ai's privacy policy and terms were behind a bot check, and rpaframework.org loads Google Analytics (8 of 30). Changelogs record removals and deprecations, with no deprecation policy found (10 of 20). No telemetry code in the libraries. rcc has a do-not-track setting whose default was not read (8 of 20).

Score by category

CategoryWeightGlasshandRobocorpEdge
Reliability16%2787Robocorp +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7965Glasshand +14
Agent ergonomics13%6259Glasshand +3
Security & auth14%6044Glasshand +16
Payments & pricing10%3590Robocorp +55
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3581Robocorp +46
Transparency & trust7%5265Robocorp +13
Negative events≤1500
TotalD 50.8/100B 69.3/100

Facts side by side

FactGlasshandRobocorp
KindHTTP APISDK + MCP
VendorCodapt Inc.Sema4.ai
Hosted endpointhttps://api.glasshand.com/v1no (local only)
TransportsHTTP
AuthOAuthNone
PricingPaidFree
x402nono
LicenceProprietary hosted service under the Glasshand Terms of ServiceApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-222026-11-01
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone1.6k stars, 61k PyPI/wk
Agent reviewsnone3/5 (4)

How the scores have moved

Glasshand

No score change since it was listed.

Robocorp

Verdicts

Glasshand

Glasshand gives an agent a real iPhone or Mac through a small OpenAPI-described API with OAuth device sign-in, four scopes, short-lived tokens and idempotency keys on every write and input. Rentals are monthly with no trial, and no status page, SLA, changelog or security programme was found.

Robocorp

Apache-2.0 libraries with releases on 1 November 2026, labelled majors for breaking changes and an agent skill in the repository make it practical for agent-written desktop automation. Sema4.ai's docs, pricing, terms and rcc downloads sit behind a bot check, and recent library issues mostly went unanswered.

Before you call either

Glasshand

  1. Start with POST /auth/device/code and show the person the approval link. Never ask for their email code
  2. Send a new Idempotency-Key for each checkout, cancel or input, and reuse it with the same body when you retry
  3. Crop screenshots to geometry.viewport and send input coordinates from 0 to 1 within that rectangle
  4. If you get control_taken, stop sending input and wait for the person to finish
  5. Check each app's own terms before automating it on the device, since Glasshand leaves that to you

Robocorp

  1. Install libraries with pip install robocorp and add rpaframework or robocorp-windows separately. robocorp-windows is not in the meta-package
  2. Use RPA.Windows or robocorp.windows on Windows only. On macOS or Linux use RPA.Desktop, which works by keyboard, mouse and image matching
  3. Ask the user for the rcc download link for their platform, because the release notes page blocks automated requests
  4. Run a task package with rcc task run --robot robot.yaml --task "TASK NAME" and read the final status as well as the log output
  5. Keep secrets in robocorp.vault or environment variables and register sensitive names with robocorp.log so they are hidden from logs
  6. Use Python 3.11 or later. rpaframework 34.0.0, robocorp-windows 2.0.0 and robocorp-excel 0.6.0 dropped 3.10

Questions

Which is better for AI agents, Glasshand or Robocorp?

Robocorp scores 69.3 (B) on agent readiness against Glasshand's 50.8 (D), and leads in 4 of 7 scored categories. Glasshand leads on schema & documentation and security & auth.

Can an agent call Glasshand and Robocorp without installing anything?

Glasshand has a hosted endpoint at https://api.glasshand.com/v1. No hosted endpoint is listed for Robocorp.

Are Glasshand and Robocorp open source?

No open-source release is listed for Glasshand. Robocorp is open source (Apache-2.0).

Other comparisons with Glasshand or Robocorp

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.