RepoRadar
Leave a Tip
Item detail
github.com

olo-dot-io/Uni-CLI

olo-dot-io/Uni-CLI is a framework in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Open on GitHub →Back to radar
Score8.9
Popularity82.0
Riskhigh
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity8.6
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for builders who need agents to do real work across software rather than stay inside one chat box. The standout value is the governed operation model: policy, evidence, and retries are built into the action layer instead of bolted on later.

Who should use it

agent platform builders automation engineers teams experimenting with computer-use agents developers who need policy and evidence on real software actions

Who should skip it

Pass on olo-dot-io/Uni-CLI if your environment cannot support the access controls and sandboxing this risk profile requires.

About this signal

olo-dot-io/Uni-CLI is tracked by RepoRadar as a framework in the Radar section. It was first seen on 2026-06-19 and last updated on 2026-06-19. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. Across RepoRadar's eight signals, olo-dot-io/Uni-CLI is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned olo-dot-io/Uni-CLI a composite score of 8.9 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 82.0 and never affects the composite score or tier. The risk label of 'high' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

This platform can sit in front of logged-in browsers, desktop apps, local tools, and files, so treat it like a high-trust automation layer and restrict its scope before using real accounts or sensitive data.

Evidence links
Closest alternatives / related signals
computer-use browser-automation mcp desktop-automation agent-ops
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-14T05:33:19.009398Z.

failed · cohort-20260714-unicli-loopback-search-extract-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-14T05:32:05.739537Z
Completed
2026-07-14T05:32:17.140441Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 3 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Installed the pinned official Uni-CLI package with lifecycle scripts disabled and started a synthetic HTML fixture on an operating-system-assigned 127.0.0.1 port.
  • Used Uni-CLI search to discover the extract command, then invoked that real command against the loopback page with JSON output and a fixed 1,200-character cap.
  • Validated the AgentEnvelope v2 success signal, exact extracted marker, and a single expected GET to the loopback fixture.
  • Executed bounded check: Use Uni-CLI's command search to discover its extract action, then extract text from a synthetic loopback-only HTML page and validate the AgentEnvelope response.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 11.40-second wall time.
Observed results
  • Check exited 1 after 11.40 seconds; failure output is retained and the verification stage must not advance.
Observed strengths
  • No product strength was established in this failed attempt; diagnostic evidence is retained.
Friction
  • This narrow check covers only deterministic static HTML extraction; dynamic browser interaction and higher-risk computer-control routes require separate permission and safety testing.
  • Setup or runtime emitted 41 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • This read-only fixture validates local command discovery, HTTP text extraction, JSON formatting, and AgentEnvelope v2 status/data; it does not exercise browser control, desktop automation, files, operating-system mutation, MCP routing, remote websites, repair loops, or policy enforcement.
  • This credential-free disposable workflow does not establish operator use, production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The local Uni-CLI package and loopback page used no account, proxy subscription, model provider, browser service, API key, or paid endpoint.

Privacy assessment: The extracted page was synthetic and served only on 127.0.0.1; npm package retrieval contacted the registry, while no page content, prompt, or repository data left the machine.

Open retained test log →

failed · cohort-20260714-unicli-loopback-search-extract-workflow-v2

Tester
RepoRadar automated local verification harness
Started
2026-07-14T05:32:41.869546Z
Completed
2026-07-14T05:32:51.668507Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 3 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Installed the pinned official Uni-CLI package with lifecycle scripts disabled, explicitly enabled its documented local-address override, and started a synthetic HTML fixture on an operating-system-assigned 127.0.0.1 port.
  • Used Uni-CLI search to discover the extract command, then invoked that real command against the loopback page with JSON output and a fixed 1,200-character cap.
  • Validated the AgentEnvelope v2 success signal, exact extracted marker, and a single expected GET to the loopback fixture.
  • Executed bounded check: Use Uni-CLI's command search to discover its extract action, then extract text from a synthetic loopback-only HTML page and validate the AgentEnvelope response.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 9.80-second wall time.
Observed results
  • Check exited 1 after 9.80 seconds; failure output is retained and the verification stage must not advance.
Observed strengths
  • No product strength was established in this failed attempt; diagnostic evidence is retained.
Friction
  • Uni-CLI correctly blocks reserved/local addresses by default, so this isolated fixture required the explicit UNICLI_ALLOW_LOCAL=1 override; dynamic browser interaction and higher-risk computer-control routes require separate permission and safety testing.
  • Setup or runtime emitted 44 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • This read-only fixture validates local command discovery, HTTP text extraction, JSON formatting, and AgentEnvelope v2 status/data; it does not exercise browser control, desktop automation, files, operating-system mutation, MCP routing, remote websites, repair loops, or policy enforcement.
  • This credential-free disposable workflow does not establish operator use, production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The local Uni-CLI package and loopback page used no account, proxy subscription, model provider, browser service, API key, or paid endpoint.

Privacy assessment: The extracted page was synthetic and served only on 127.0.0.1; npm package retrieval contacted the registry, while no page content, prompt, or repository data left the machine.

Open retained test log →

passed · cohort-20260714-unicli-loopback-search-extract-workflow-v3

Tester
RepoRadar automated local verification harness
Started
2026-07-14T05:33:08.948102Z
Completed
2026-07-14T05:33:19.009398Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 3 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Installed the pinned official Uni-CLI package with lifecycle scripts disabled, explicitly enabled its documented local-address override, and started a synthetic HTML fixture on an operating-system-assigned 127.0.0.1 port.
  • Used Uni-CLI search to discover the extract command, then invoked that real command against the loopback page with JSON output and a fixed 1,200-character cap.
  • Validated the AgentEnvelope v2 success signal, exact extracted marker, and a single expected GET to the loopback fixture.
  • Executed bounded check: Use Uni-CLI's command search to discover its extract action, then extract text from a synthetic loopback-only HTML page and validate the AgentEnvelope response.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 10.06-second wall time.
Observed results
  • Command exited 0 after 10.06 seconds.
  • Uni-CLI discovered its extraction capability and returned the unique HTML marker in a successful schema-v2 JSON envelope after exactly one local HTTP request.
  • Expected marker 'CHECK_OK search=extract command=extract schema=2 marker=true' was observed in retained output.
  • Validated result.json: 6 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
  • Validated transcript.json: 5 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The CLI exposes searchable action discovery and a consistent machine-readable envelope around read-only web extraction, which is useful for agent orchestration.
Friction
  • Uni-CLI correctly blocks reserved/local addresses by default, so this isolated fixture required the explicit UNICLI_ALLOW_LOCAL=1 override; dynamic browser interaction and higher-risk computer-control routes require separate permission and safety testing.
  • Setup or runtime emitted 2 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • This read-only fixture validates local command discovery, HTTP text extraction, JSON formatting, and AgentEnvelope v2 status/data; it does not exercise browser control, desktop automation, files, operating-system mutation, MCP routing, remote websites, repair loops, or policy enforcement.
  • This credential-free disposable workflow does not establish operator use, production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The local Uni-CLI package and loopback page used no account, proxy subscription, model provider, browser service, API key, or paid endpoint.

Privacy assessment: The extracted page was synthetic and served only on 127.0.0.1; npm package retrieval contacted the registry, while no page content, prompt, or repository data left the machine.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

36 dated snapshots retained from 2026-06-19 through 2026-08-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.9 current · +0.0 net
Repository momentum9.0 current · +1.0 net
GitHub stars (observed)90 current · +2 net
GitHub stars90 exact observation
Versionv1.0.2
Last release2026-08-02T12:34:47Z
Maintenanceactive
Current riskhigh
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineClaude Code, Model Context Protocol, OpenAI, OpenAI Codex

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-038.99.090hightry nowactive
2026-08-028.99.090hightry nowactive
2026-08-018.99.090hightry nowactive
2026-07-318.98.0Not recordedhightry nownot recorded
2026-07-308.98.0Not recordedhightry nownot recorded
2026-07-298.99.390hightry nowactive
2026-07-288.99.089hightry nowactive
2026-07-218.99.087hightry nowactive
2026-07-208.99.087hightry nowactive
2026-07-198.99.087hightry nowactive
2026-07-188.99.087hightry nowactive
2026-07-178.99.087hightry nowactive

Why the record changed

version changed

Version changed: v1.0.1 → v1.0.2.

stars changed

Stars changed: 89 → 90.

stars changed

Stars changed: 87 → 89.

version changed

Version changed: v0.400.0 → v0.400.2.

version changed

Version changed: v0.227.1 → v0.400.0.

stars changed

Stars changed: 88 → 87.

verification changed

Verification changed: Discovered → Tested in a bounded workflow.