Skip to content
Universal computer-control platform for agents

Uni-CLI

Browsers, MCP, sandboxes, desktops, and local tools are fingers of one hand.

Uni-CLI turns 313 websites and tools, logged-in browsers, desktop apps, local commands, files, MCP servers, accessibility trees, screenshots, and system capabilities into searchable, governed, observable, repairable operations. Agents select an action substrate by intent, execute with policy, receive evidence, then diagnose, repair, or reroute until the result is delivered.

Intent searchPolicy gatedAgentEnvelope v2MCP + ACPDesktop AXVisual fallbackSelf-repair
First commandv0.225.1 · Apollo · Conrad
npm install -g @zenalexa/unicli
unicli search "find AI agent discussions on reddit"
unicli agents recommend codex
unicli mcp serve --transport streamable --port 19826

Not a wrapper. Not a tool list. The hand agents use to control computers.

People open apps and look for buttons. Agents need a steadier hand: understand intent, choose an API, browser, desktop, subprocess, protocol, or visual substrate, act with permissions and arguments, and receive a structured receipt. Uni-CLI turns that chain into a platform across CLI, MCP, ACP, skills, and local runtimes.

IntentBilingual BM25 search maps a task to operations, arguments, auth posture, risk, and examples.
SubstrateWeb APIs, cookie sessions, browser CDP, macOS AX, external CLIs, protocols, and visual fallback share one control kernel.
EvidenceMarkdown is the agent-friendly default, with JSON, YAML, CSV, compact output, and run evidence for review.
Repair or rerouteErrors carry source path, failed step or boundary, retryability, suggestions, and alternatives for local override or delivery reroute verification.

Why it matters

What does this add for an agent?

A universal computer-control hand. Sites, desktop apps, local commands, files, and protocol servers become governed operation contracts instead of one-off API guesses, selector guesses, and output guesses.

Why not just drive the browser directly?

Direct operation is the last mile. Uni-CLI compiles reusable paths into commands first, then falls back to browser, desktop AX, or visual input when the semantic path is not enough.

What happens when a site or app changes?

The error envelope gives the adapter file, failed step, and suggestion. Agents can patch a local override and verify with repair; local apps route through platform transports and visual fallback.

How does MCP fit?

MCP is one exposure/protocol substrate. The core pieces are operation contracts, the control kernel, output receipts, permission policy, and the delivery/repair loop.

How a task controls a computer

Current surface

These numbers come from the current generated repo artifacts: operations, adapters, pipeline steps, tests, and substrates are counted by the build.

sites and tools
313
operations
1767
pipeline steps
103
tests
9120

What it can control today

Web and communities

Public APIs, cookie sessions, RSS, search, downloads, publishing, and Chinese platforms.

Browser actions

CDP navigation, clicks, typing, intercepts, screenshots, snapshots, and before/after evidence.

Desktop and local

macOS AX, background input, Office, design tools, media tools, containers, and local subprocesses.

Agent protocols

MCP stdio / Streamable (legacy `sse` alias), ACP, agent matrix, skills export, and config generation.

Start here

  1. InstallInstall the CLI, run the first search, and learn output formats plus exit codes.
  2. Operation catalogFind operations by site, substrate, auth mode, and examples.
  3. Repair adaptersRead YAML, pipeline steps, the repair flow, and verification commands.
  4. Connect agentsNative CLI, MCP, ACP, agent configs, and skills export.
Agent-readable index/llms.txt/llms-full.txt

Released under the Apache-2.0 License