More Tools for Agents

Agents can analyze and plan, but execution still depends on real-world tools. oo-cli connects them to those tools so they can actually get work done.

Read the install guide View GitHub

Click to copy the oo-cli install command for your system.

# installs latest: oo-cli 0.2.27
# sign in with your OOMOL account and confirm the CLI is ready
# searches packages and connector actions together
# narrow it down to published packages before choosing one
# inspect schema, version, and runnable blocks before execution
# execute the selected package block
# fetch the result back in the terminal

What oo-cli Covers Now

Set it up, find a ready-made tool, then run the task

This page does not need to unpack every command. The main job is simpler: get oo-cli into the terminal, use it to find a ready-made tool, then run the task and bring the result back. The detailed command surface belongs in the docs.

Setup

oo install / oo update / oo skills install

Connect oo-cli to the terminal and host apps

Use the official install command to put oo in the terminal, then install the needed skills into Codex, Claude Code, and other supported hosts.

Clear install and update path
Keep working from the same place

Discover

oo search / oo packages info / oo connector search

Search ready-made tools before building your own

Search packages and connectors first, then inspect package metadata or connector schemas to confirm whether a reusable capability already exists.

Understand inputs and capability boundaries first
Reduce unnecessary custom builds

Run

oo connector run / oo cloud-task ... / oo file / oo log

Run, wait for results, and inspect logs in one path

Short tasks can run directly through connectors. Longer jobs can go through Cloud Task. Waiting, fetching results, files, and logs all stay inside oo-cli.

Supports dry-run and long task tracking
No separate admin console needed to finish the job

Current Path

This is roughly how a real task gets moving

Install and log in first, then search and confirm the tool. If it can run directly, run it directly. If it takes longer, wait for the result to come back. The detailed commands and parameters live in the docs.

One real task usually looks like this

# install oo-cli with the official install command, then sign in$ curl -fsSL https://cli.oomol.com/install.sh | bash$ oo login# search and confirm whether it is the right tool$ oo search "generate a QR code for OOMOL"$ oo packages info foo/bar@latest# run it directly, or wait for the longer job to come back$ oo connector run <serviceName> -a <action> --dry-run --data @input.json$ oo cloud-task run foo/[email protected] -b main --data @input.json$ oo cloud-task result task_123

Need More?

When ready-made tools are not enough, use Studio or Cloud

Let oo-cli establish the published-tool path and the install/update lifecycle first. If you need to build your own tool or keep it running continuously, then move on to Studio or Cloud.

Go to Studio to generate or complete your own tool

When existing tools are not enough, use Studio to let the agent generate code, fill in parameters, and validate the tool locally.

Explore Studio

Go to Cloud when it needs stable runtime and delivery

When the tool needs stable runtime, logs, or broader reuse, let Cloud take over.

Explore Cloud

Let your agent use these tools now

Install oo-cli with the official install commands, then use it to search tools, inspect inputs, and run a real task from the terminal.

Read the install guide Read the command reference