BxPlaywright vs Pomerado

BxPlaywright 53

The snapshot build of 23 October 2026 is the latest published package, so 30 on time, though it isn't a release (30). No tagged releases or dated changelog entries in the 90 days, only one version rebuilt (0 of 20). 39 pull requests merged by Luis Majano between 30 September and 23 October. Issue replies couldn't be read and bugs go to Jira (10 of 25). Not in the official MCP registry, and the ForgeBox package has no stable version (5 of 15). Playwright for Java 1.63.0, Dependabot for Gradle monthly and Actions quarterly, a daily test run and a format check (8 of 10). 30+0+10+5+8 = 53.

Pomerado 81

npm 0.4.0-canary.194 on 17 October 2026, the API change of 15 October and the registry entry of 15 October (30). Releases 0.1.0 to 0.2.0 between 5 and 6 October and more than 150 canaries since (20). About 650 merged pull requests in 12 days, nearly all by the two founders. GitHub issues and replies couldn't be read, because the GitHub API refused this session, so this rests on the commit history and the founders' email address (8 of 25). In the official MCP registry as ai.pomerado/pomerado, a domain-verified namespace, active since 15 October 2026 (15). CI runs a gitleaks secret scan, pins actions by SHA and publishes with npm provenance. Run results couldn't be read (8 of 10).

BxPlaywright 43

Library reading, as puppeteer and playwright-mcp were. No credential to leak and nothing to scope, so the middle band (20 of 30). Nothing is restricted by default. browser_visit takes any URL with no allow-list, browser_screenshot writes to any path the model passes, and the tools are added to bx-ai's global registry unless registerAiTools is false, so an agent given every registered tool gets a browser. Over MCP it starts Microsoft's server, which limits file access to workspace roots, and Ortus's plugin starts it with --headless but without --isolated, with browser_run_code_unsafe and browser_evaluate in the default set. HTTPS errors are not ignored by default (6 of 20). Page snapshots and text go to the model unfenced, and the docs give no prompt-injection guidance (0 of 15). Screenshot, trace and video policies, show-trace, and interception points such as onPageCreate and onPlaywrightArtifact give the operator a record, all off by default (10 of 15). CONTRIBUTING.md asks for reports to security@ortussolutions.com and the Slack #security channel; SECURITY.md points there. No security.txt (410, per the boxlang-ai check of the same day), no bounty, no advisories. Node.js downloads are checked against the release's SHA-256 list (7 of 20). 20+6+0+10+7 = 43.

Pomerado 69

OAuth for MCP clients, and pom_ API keys limited to chosen permissions out of 11, expiring after 90 days by default, rotated and revoked through the API, with integration keys confined to one site's MCP. No secret travels in a URL; the keyless URL refuses a key (30). The read-only run refuses a tool that writes before a job starts, builds declare read or write, write tools carry destructiveHint, website logins go through a protected page, and a key can't reveal a saved password or authenticator code. No approval step of Pomerado's own for writes was found beyond the client's own prompt (16). Tools return website content. The job-object page says to treat a job's message as data, never as instructions, and outputs are checked against each tool's schema, but no wider guidance on untrusted page text was found (6). Run logs list each browser action and the site's own requests, kept 90 days, builds have an activity log, and connected apps show permissions used and last use (13). No security.txt, SOC 2, ISO 27001 or bug bounty found. The README sends reports to GitHub private vulnerability reporting, and the terms commit to notify customers of incidents without undue delay (4). Pomerado stores website passwords, authenticator secrets and recovery codes, which raises the stakes of that gap.

BxPlaywright 66

Library reading. BoxLang is dynamically typed. The public API is listed in the docs' integrations page, help() and bxplaywright help --json describe it at run time, and the ten agent tools describe each argument in a sentence, with no published API reference (14 of 25). llms.txt with a Markdown copy of each of 18 docs pages (10). The AI page says when to use aiTools(), the registry or MCP, and when to turn registration off. Tool descriptions are one line each (13 of 20). Every agent-tool argument is a string, with no enums or limits; library options are checked, and InvalidOption lists the valid values (9 of 15). An errors page lists each error type with when it happens and the fix, eight runnable examples sit in the repository, and the docs have code on every page (13 of 15). Keep a Changelog and docs versioning on release, but no released version and no tags yet (7 of 15). 14+10+13+9+13+7 = 66.

Pomerado 86

OpenAPI 3.1 at /v1/openapi.json with 84 operations on 66 paths, and every MCP tool on the keyless endpoint has a typed JSON Schema input with additionalProperties: false (25). llms.txt with every page, and a Markdown twin of each docs page (10). MCP descriptions say when to use each tool and when not to, such as Pomerado before a browser, the read-only run for read tools, possible_matches before a build, and secrets on answer_url, not in chat. The server's instructions say to use a browser only if Pomerado says it can't build a tool (18). 159 enums, lengths and ranges such as limit 1 to 100 and keys of 1 to 200 characters, and required fields marked. The run and build tools take input and example_input as JSON-encoded strings over MCP (11). 58 of 84 operations carry examples, all 84 document error responses, and the errors page gives 132 codes, each with its status, whether to retry and what to do (14). Paths are versioned /v1. The API reference has a dated Changes list with one entry, of 15 October 2026, and the open-source core keeps CHANGELOG.md with breaking-change sections (8 of 15).

BxPlaywright 63

Library reading, scored on what a tool-calling agent gets. Ten compact in-process tools for BoxLang AI, with nothing to load until a tool is used (25 for ten or fewer), less 5 because every action tool returns the whole page's AI snapshot. Through MCP an agent gets Playwright's 24 default tools (20 of 25). The agent tools have no depth, selector or size limit, and browser_text returns the whole page. snapshot( selector ) exists in the library but not in the tools (8 of 20). Errors come back to the agent as text in the form Error [type]: message Fix: detail, and the error types are documented (16 of 20). Assertions retry until they pass. The in-process tools carry no read-only or destructive hints, and bx-ai doesn't read them; over MCP the annotations are Microsoft's (8 of 20). Works with defaults (headless Chromium, 1280 by 720) and profiles, but in one language, BoxLang, with the MCP route for any other client (11 of 15). 20+8+16+8+11 = 63.

Pomerado 83

The keyless endpoint lists eight tools with about 24,000 characters of definitions, and the docs give 14 for a signed-in connection, with the rest of the API reached through search_pomerado_api, describe_pomerado_api and call_pomerado_api instead of one tool per operation. An integration MCP narrows an agent to one site's tools (19 of 25). Lists take cursor and limit 1 to 100, tool search filters by query, site and integration, get_job takes include_result and wait_seconds, and paged results carry a cursor (17). One error envelope with code, message, retryable, docs_url and details, and codes such as key_permission_missing name the missing permission and the page to fix it (20). Idempotency keys on runs and builds, with replay marked Idempotent-Replayed, and every keyless tool carries readOnlyHint or destructiveHint, idempotentHint and openWorldHint as fits (20). Few required fields (none for search, two for a run), but no official client SDK. The npm package is the local minter, not a Cloud client (7 of 15).

BxPlaywright 60

Free, self-hosted, nothing to buy, so 20 + 20 + 20. The BoxLang runtime's paid plans aren't needed for this module. No payment protocol (0). 60 in all.

Pomerado 42

No x402, MPP or L402 on Pomerado's endpoints (0). Plan prices are public, Free $0, Premium $50 a month and Business custom, with call and build allowances, but there is no per-call price (10). The Free plan and keyless use need no card (20). An agent can find and run 46 public read-only tools with no account, but writes, logins and builds need an account that a person approves, through OAuth or a device code, so partial credit (12 of 20).

BxPlaywright 70

Apache-2.0, OSI approved, in box.json and src/main/resources/LICENSE (30). Local software with no data statement for the module. The source contacts only nodejs.org, Playwright's browser downloads and the pages it is told to open, and Ortus's privacy policy covers its website and customers (15 of 30). The integrations page says a minor release only adds and removals wait for a major release, listed in the changelog. Nothing has been released under it, and the module was renamed from playwright to bxplaywright on 12 October before any release (10 of 20). No telemetry found in the source and no statement either way in the docs, scored as boxlang-ai was (10 of 20). 30+15+10+10 = 65.

Pomerado 53

The hosted service is closed with clear terms (Common Paper Cloud Service Agreement 2.1, last updated 4 October 2026), and the complete minting core is MIT on GitHub, which the README says the Cloud runs (24). The privacy policy is an iubenda embed whose path iubenda's robots.txt disallows, so it was not read. The homepage FAQ says results are erased once read or within 60 minutes, credentials are kept only if saved, and hashes of sign-in identifiers are retained, and the API docs keep run logs for 90 days. No public DPA found (10 of 30). No deprecation policy found. The tool docs promise that a repair never removes or loosens an output field unless the site stopped showing it and the person confirms, and the terms give 30 days' notice of price changes (7). No subprocessor list or data location found. The open-source README says builds use OpenAI models (2).