For the complete documentation index, see llms.txt. This page is also available as Markdown.

OpenClaw

OpenClaw is an independent open-source AI agent tooland provides highly customizable Agent runtime and interaction services, developed by an independent open-source team.

For ordinary users who want to experience OpenClaw's powerful capabilities, Cherry Studio provides a one-click integration interface. You don't need to tinker with complex low-level commands, runtime dependencies, and proxies yourself; you can directly reuse the preconfigured model service (Provider) inside Cherry Studio to start the OpenClaw hosted service with one click.

Do I need OpenClaw?

  • General users: If you only use agents daily in the Cherry Studio client GUI, just refer to agents that's all,does not require to enable OpenClaw.

  • Try it out / power users: If you want to experience the OpenClaw project in a terminal or standalone workflow, you can use this module to quickly start the Gateway service.

Install OpenClaw

Click + ➡️ Launcher ➡️ Click OpenClaw the icon in the top tab bar. When you enter for the first time, you will see:

OpenClaw is not installed
  • Click Install OpenClaw ➡️ Cherry Studio will automatically download from the official source and install the latest OpenClaw runtime binary package.

  • After installation, the page will switch to the "Running / Stopped" status, and you can one-click here Start or stop the local OpenClaw Gateway.

Configure Provider and model

In the OpenClaw configuration panel:

  1. Select the Provider service(must be a platform already configured in Settings → Model Services the platform).

  2. Select the specific Model.

  3. Click Start button, and the OpenClaw Gateway will listen on a local port and start serving.

Use in the OpenClaw CLI

After one-click startup, run openclaw directly in your terminal to call the compute power and models hosted and started in Cherry Studio.

  • For a detailed CLI usage guide, please read the official documentation:https://docs.openclaw.ai/

  • You can also directly click the Documentation Go directly there.

and agents fundamental positioning difference

The two are not simply divided into "command line vs. graphical interface"; their positioning in Cherry Studio is completely different:

Dimension
Cherry Agent (built-in agent)
OpenClaw

Running location

Runs natively inside the client (Cherry Studio)

Independent external process Gateway

Product positioning

Tools and workflow agents deeply and natively integrated with the client UI

For users who want to try it out Greatly reduces the underlying dependencies, proxies, and environment configuration costs of the OpenClaw project

Interaction interface

Cherry Studio graphical chat window

Terminal CLI interaction or other clients that support the OpenClaw API

Runtime dependencies

Must rely on the API server

independent Gateway, with one-click environment hosting provided by Cherry Studio

Tips and tricks

  • OpenClaw and the built-in Cherry Agent can be used in parallel in the system without interfering with each other.

  • After OpenClaw Gateway starts on a machine, it will occupy its specific local port (see the OpenClaw documentation for details), and the built-in Cherry Studio API server default listening 23333 ports are completely separate and do not interfere with each other.

  • When the Cherry Studio software is closed, the hosted and started OpenClaw Gateway service will stop automatically; if you need it to run persistently in the background for a long time, it is recommended to use OpenClaw's official built-in daemon mode.


💡 Get help and submit feedback

If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to Feedback and Suggestions the official channel provided in OpenClaw official repository participate in open-source discussions.

Last updated

Was this helpful?