oo-cli - More Tools for Agents
logo
oo-cliPrimary entry: install officially, then search, inspect, and use tools directlyOOMOL StudioBuild, combine, and orchestrate your own tools when connected services and published tools are not enoughOOMOL CloudDeliver tools back through oo-cli with hosted cloud runtimeOOMOL AIOptional GUI: use the same capabilities through a chat interface
DownloadDocsPricingChangelogBlog
Community

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 guideView 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 the hosts people already use

Use the official install commands to get oo into the terminal, then connect the skills you need to hosts such as Codex and Claude Code.

  • Clear install and upgrade path
  • No separate place to switch to
Discovery
oo search / oo packages info / oo connector search

Find the ready-made tool first before deciding to build

Search packages and connectors in natural language, then inspect package metadata or connector schemas to confirm whether a published capability already fits.

  • Understand inputs and scope first
  • Avoid rebuilding what already exists
Run
oo connector run / oo cloud-task ... / oo file / oo log

Execute, wait, fetch results, and inspect logs in the same path

Direct connector calls work for short jobs. Cloud Task handles longer ones. Waiting, results, files, and logs still stay inside oo-cli instead of another backend.

  • Dry-run and long-task tracking are built in
  • No need to switch tools 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 guideRead the command reference