OpenClaw CLI setup

OpenClaw can execute media tasks through EvoLink CLI. This page covers host environment and skill differences; installation and sign-in owns the complete common procedure. For native tools, use the MCP guide directly.

Ask your agent to install

Paste the following into the agent conversation. It matches the website prompt. Complete browser sign-in and permission review yourself.

Set up EvoLink so I can generate images, video and audio directly here.
Install the CLI: run `npm install -g @evolinkai/cli`.
Sign in: run `evolink auth login`.
Install the companion skill: run `evolink skills install`.
Verify the connection. Once successful, tell me I can get started.

Three steps for this client

Complete common installation and sign-in

Install for the machine and user running the Gateway; reload skills using the host workflow when needed. Desktop success does not prove remote availability.First-time users should open the five-step guide: check Node.js 22+, install CLI, and complete browser sign-in. It includes commands, success indicators, and troubleshooting. If already done, verify:

evolink --version
evolink auth status --json

Look for a CLI version and authenticated: true. See installation errors, sign-in errors, or SSH callbacks for the failed stage.

Synchronize this agent's skill and verify discovery

evolink skills install --agent openclaw
evolink skills status --agent openclaw --json

The directory is ~/.openclaw/skills/evolink-cli. current: true means files match the CLI. Ask the agent:

Confirm this session can discover and read the evolink-cli skill. Verify access without generating media.

assistant_discovery: not_checked still requires host verification. Follow skill discovery if files exist but are unused. Review required execution permissions and preserve personal modifications.

Verify for free before creating media

evolink balance --json
evolink doctor --agent openclaw --json

Setup is complete when balance returns account data, doctor reports ok, connection_verified, and model_discovery_verified as true, and the agent confirms reading the skill. These queries do not create paid media tasks. Zero balance can still verify connectivity.

Combined setup for an installed CLI

evolink setup --agent openclaw --json

This checks the environment, synchronizes skills, signs in when needed, and verifies access. Look for setup_complete: true; host discovery still needs confirmation. Use phase, steps, error, and recovery to identify failures.

Update and sign out

After updating the CLI, synchronize the current agent’s skill:

npm install -g @evolinkai/cli@latest
evolink --version
evolink skills install --agent openclaw
evolink skills status --agent openclaw --json

Local changes are preserved; handle modified or conflict under skill troubleshooting. Run the following only when you want to sign out of the CLI; it is not an installation or update step.

evolink auth logout

Troubleshooting starting points

Symptom	Next step
Missing npm/evolink, permissions, installation timeout	Environment and installation
Browser did not open, OAuth timeout, credential storage error	Login and callbacks; SSH login
Skill installed but agent does not use it	Skill discovery and execution permission
Submitted task timed out or result was lost	Recover the original task

After connecting, follow the first media workflow: inspect models, parameters, and costs, approve, then submit. Full commands are in CLI command reference.

Start here

CLI

MCP

Shared resources

Ask your agent to install

Three steps for this client

Combined setup for an installed CLI

Update and sign out

Troubleshooting starting points

​Ask your agent to install

​Three steps for this client

​Combined setup for an installed CLI

​Update and sign out

​Troubleshooting starting points

Ask your agent to install

Three steps for this client

Combined setup for an installed CLI

Update and sign out

Troubleshooting starting points