Head to head · Evaluations · October 2026 research run

Gauge CLI vs Hue

Gauge CLI scores 62.9 (B) on agent readiness against Hue's 56.7 (C), and leads in 2 of 7 scored categories. Hue leads on schema & documentation, agent ergonomics, security & auth and transparency & trust. Both do evaluations.

Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons

Which one, for what

Gauge CLI B

Best for Teams that build skills, CLIs, SDKs or MCP servers and want to see where coding agents get stuck with them, and to test fixes before release.

Ahead on

  • Reliability, 60 against 30
  • Payments & pricing, 60 against 0

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Collects anonymous command usage by default, with an opt-out

Hue C

Best for Teams testing agents that act in Gmail, Slack, Salesforce, Notion, Linear and similar apps who want stateful simulated copies seeded from traces or a description.

Ahead on

  • Schema & documentation, 68 against 60
  • Agent ergonomics, 88 against 75
  • Security & auth, 74 against 55
  • Transparency & trust, 59 against 53

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No self-serve sign-up found. Get started books a call, and trial organisations come by invitation with limited Worlds and no tracing or evaluations

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.

Payments & pricing Gauge CLI +60

Gauge CLI 60

Scored on the hosted option. No payment protocol (0). Credit prices weren't found on the pages read (0). Local mode is free with no card (20). Local mode needs no sign-up (20). 0 + 0 + 20 + 20 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Hue 0

No x402 or other machine payment found (0). No pricing page. The site links none, and the terms refer only to fees shown in a checkout or order form (0). No free tier open to all. Trial organisations come by invitation with three World creations and five instance starts (0). Get started books a call on cal.com, and the app answers with a sign-in page (0). 0+0+0+0 = 0.

Reliability Gauge CLI +30

Gauge CLI 60

Local package. Installs from npm as @withgauge/cli with Node 22.13 or later and Docker stated (20). checks.yml runs npm run check on push and pull request across a matrix, and the repository has 76 test files; whether main passes wasn't read (20 of 25). Issues weren't read (5, unchecked). A dated changelog with Added sections per release (15). Version 0.28.0 (0). 20 + 20 + 5 + 15 + 0 = 60.

Hue 30

No status page found. The site, docs and SDK repository link none (0). With no history to read, 5. No request rate limits for the API or MCP server are published. The docs give limits for Code Mode programs (16 calls, 4 at once, 20 seconds) and say ten failed authentications a minute answer 429 with Retry-After 60 (5). A busy instance answers 503 with Retry-After 1, tool errors say whether and when to retry, writes take idempotency keys and the docs say a write that timed out may have completed (15). No SLA found, and the terms carry none (0). The site calls this a public launch, but the SDKs are 0.x and trial organisations get a reduced product (5). 0+5+5+15+0+5 = 30.

Security & auth Hue +19

Gauge CLI 55

Local tool. Agent credentials stay on your machine in local mode; hosted login with a device flow (20 of 30). Test agents run in fresh Docker sessions with injected inputs, and the gateway brokers credentials in hosted mode (12 of 20). Agents under test read your product's docs and outputs, with no prompt-injection guidance (5 of 15). Local transcripts and SQLite evidence per run (10 of 15). No security policy found (8 of 20). 20 + 12 + 5 + 10 + 8 = 55.

Hue 74

OAuth with dynamic client registration and PKCE, scopes mcp:read and mcp:write in the 401 answer, one-hour access tokens and revocation under Connected apps. Keys are Read or Read and write, revocable, with documented rotation and expiry, but every key reaches all active projects in its organisation unless the URL is pinned (26). A Read key and ?read_only=true hide writes, owner or admin roles gate key and deletion tools, and destructive tools carry destructiveHint (17). Recorded content is opt-in per call, marked untrusted and audited (12). Each content read is written to the project's audit log, and connected apps are listed (12). SECURITY.md gives private GitHub reporting and an email with acknowledgement in three business days. No security.txt and no bug bounty found. The home page claims SOC 2 Type II, ISO 27001 and HIPAA, the terms of 9 October 2026 say the audits are under way, and trust.hue.run is closed to ClaudeBot (7). 26+17+12+12+7 = 74.

Agent ergonomics Hue +13

Gauge CLI 75

CLI reading for an agent driving it. Bundled instructions match the installed version, and output is filterable with -o json (20 of 25). Run summaries and Findings with queryable fields (15 of 20). Errors not documented as a reference (10 of 20). Reruns from checkpoints and a recheck command with a confirm step (15 of 20). Four commands to start, Node only (15 of 15). 20 + 15 + 10 + 15 + 15 = 75.

Hue 88

About 217 tools in all, but a default connection lists 18 (15 production reads and three catalogue tools), with named toolsets, a read-only switch and a four-tool Code Mode (15, plus 7 for the subsets). Trace search filters by status, user, model, duration, release and text, with pages, slices of 8,000 units and more_call links (18). Errors carry a code, message, hint, retryable and retry_after_ms (18). Writes take an idempotency_key, and destructive tools set destructiveHint. Read-only hints weren't seen, since the tool list couldn't be read (15). Official TypeScript and Python SDKs and a CLI (15). 22+18+18+15+15 = 88.

Schema & documentation Hue +8

Gauge CLI 60

CLI reading. No machine-readable contract, -o json on read commands (10 of 25). No llms.txt; instructions bundled in the CLI for agents (5). The README says what it finds and when local or hosted fits (16 of 20). Commands with help text; typed flags (9 of 15). Worked examples, no error reference (8 of 15). Dated changelog and semver tags (12 of 15). 10 + 5 + 16 + 9 + 8 + 12 = 60.

Hue 68

The MCP server publishes typed schemas through search_hue_tools, which returns input_schema and annotations for each tool, but the server answers 401 without an account, so no schema was read. No OpenAPI file found (10). llms.txt and a Markdown copy of every page (10). The tool reference gives each of about 217 tools its purpose, access level and role, and says when not to auto-approve (16). Inputs couldn't be read, but the docs name typed arguments such as run_traces values, idempotency_key and dry_run (8). Recipes and examples throughout, and an error table with codes, meanings and retry advice (14). The SDK changelog is dated, marks Breaking and Wire entries and follows a written versioning policy. Renamed tools answer not_found naming the replacement. No product or MCP changelog found (10). 10+10+16+8+14+10 = 68.

Transparency & trust Hue +6

Gauge CLI 53

MIT (30). Local data stays in .gauge/ and telemetry fields are listed; hosted data handling wasn't read (18 of 30). Dated changelog, no deprecation policy (10 of 20). Telemetry on by default, disclosed with an opt-out (20). 30 + 18 + 10 + 20 = 78.

Hue 59

Closed platform with terms from Hue Intelligence Inc. (last updated 9 October 2026, New York law). SDKs under MIT (15). The privacy policy of 28 October 2026 gives no retention periods. The docs say telemetry retention is set per project and nothing expires without a policy, the terms rule out training general models on customer content and require a DPA before personal data, and the docs name what goes to TypeSafe and the Vercel AI Gateway. These agree but leave gaps (18). Renamed tools point to their replacements, legacy key presets keep working, and the terms promise 30 days' notice of price rises. No dated deprecation notices (8). Subprocessors are named only by category in the privacy policy and no data location was found (8). 15+18+8+8 = 49.

Score by category

CategoryWeightGauge CLIHueEdge
Reliability16%6030Gauge CLI +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6068Hue +8
Agent ergonomics13%7588Hue +13
Security & auth14%5574Hue +19
Payments & pricing10%600Gauge CLI +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8283Hue +1
Transparency & trust7%5359Hue +6
Negative events≤1500
TotalB 62.9/100C 56.7/100

Facts side by side

FactGauge CLIHue
KindSDK + MCPHTTP API
VendorGaugeHue
Hosted endpointno (local only)https://mcp.hue.run/mcp
TransportsStreamable HTTP, HTTP
AuthNoneOAuth or key
PricingFreemiumPaid
x402nono
LicenceMITnone
Tools exposednone217
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-11-042026-11-12
Terms last updatedno document linked2026-10-09
Privacy policy last updatedno document linked2026-10-28
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text

How the scores have moved

Gauge CLI

Hue

No score change since it was listed.

Verdicts

Gauge CLI

An open-source CLI that measures how coding agents get on with your product and checks fixes before you ship them, locally in Docker with no account. It's young and pre-1.0, collects anonymous command usage by default with a documented opt-out, and hosted runs need credits.

Hue

Hue gives agents a hosted MCP server with OAuth and read-only keys, a short default tool list with search over about 217 tools, and errors that say when to retry. Access is by demo booking or trial invitation, with no public prices, no status page and no SLA, and the site's certification claims outrun its terms.

Before you call either

Gauge CLI

  1. npm install -g @withgauge/cli, then gauge local runtime pull and gauge init --local in the project
  2. Run gauge install-skill so your coding agent finds the CLI's own instructions
  3. Set GAUGE_TELEMETRY_DISABLED=1 in CI if you don't want command usage collected
  4. Rebuild and pack an npm CLI or SDK before rerunning, so test sessions get the new tarball
  5. Keep .gauge/ private; it holds measurements and analyses

Hue

  1. Connect to https://mcp.hue.run/mcp with ?toolsets=all only if your client defers tool definitions, otherwise keep the default 18 tools and call search_hue_tools
  2. Use a Read key or ?read_only=true for inspection, since sign-in grants Read and write to every active project
  3. Read the retryable flag before retrying a failed tool, and on a write that timed out read its state first
  4. Reuse the same idempotency_key when retrying create_world, launch_run, edit_world or send_instance_input
  5. Treat recorded span content as untrusted data, and request it only when needed, because every read is audited

Questions

Which is better for AI agents, Gauge CLI or Hue?

Gauge CLI scores 62.9 (B) on agent readiness against Hue's 56.7 (C), and leads in 2 of 7 scored categories. Hue leads on schema & documentation, agent ergonomics, security & auth and transparency & trust.

Can an agent call Gauge CLI and Hue without installing anything?

No hosted endpoint is listed for Gauge CLI. Hue has a hosted endpoint at https://mcp.hue.run/mcp.

Are Gauge CLI and Hue open source?

Gauge CLI is open source (MIT). No open-source release is listed for Hue.

Other comparisons with Gauge CLI or Hue

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.