Skip to main content

​
Overview

OpenClaw is a self-hosted AI agent platform for running assistants across chat, messaging channels, tools, skills, and automations. OpenClaw can expose its agents through an OpenAI-compatible Gateway. After you enable the Gateway, EnConvo can use an OpenClaw agent like any other AI model, including inside chat, EnConvo agents, and model-powered features. OpenClaw’s Gateway exposes OpenAI-compatible endpoints such as /v1/models, /v1/chat/completions, and /v1/responses. EnConvo’s OpenClaw provider uses the Chat Completions API (/v1/chat/completions).
EnConvo does not use the OpenClaw Responses API for this provider. Configure OpenClaw through its OpenAI-compatible Chat Completions Gateway.
New to OpenClaw? Start with the OpenClaw Getting Started guide, then return here to connect it to EnConvo.
See the OpenClaw Gateway docs for the full Gateway endpoint reference.

​
What You Need

  • OpenClaw installed on the machine that will run the Gateway
  • The OpenClaw Gateway running on a reachable host and port
  • The Chat Completions Gateway endpoint enabled
  • The Gateway token from ~/.openclaw/openclaw.json
  • EnConvo with the OpenClaw AI model provider enabled

​
Automatic Setup in EnConvo

Open EnConvo Settings -> AI Model -> OpenClaw. The setup card can start, stop, and configure the local OpenClaw Gateway for you. Use Auto Setup when OpenClaw is installed on the same Mac as EnConvo. EnConvo will:
1

Find OpenClaw

Check that the openclaw CLI exists on this Mac.
2

Enable Chat Completions

Run openclaw config set gateway.http.endpoints.chatCompletions.enabled true.
3

Prepare the Gateway token

Read gateway.auth.token from ~/.openclaw/openclaw.json, or create one if it is missing.
4

Start the Gateway

Start or restart the OpenClaw Gateway service.
5

Verify the API

Probe the Gateway with /health and /v1/models.
6

Save credentials

Save the base URL and Gateway token into EnConvo’s OpenClaw credentials.
The setup card shows a runtime badge such as Running or Stopped. While the card is visible, EnConvo refreshes this status periodically and stops refreshing when the card is no longer visible.

​
Enable OpenClaw Gateway

You can ask OpenClaw to prepare the Gateway details for you:
Use the returned base URL and token in EnConvo’s OpenClaw credential settings.
1

Enable Chat Completions

Enable the OpenAI-compatible chat completions endpoint once:
2

Choose the bind mode

For local-only access, keep the default loopback bind. For another device on your LAN to reach the Gateway, bind to LAN:
3

Restart the Gateway

Apply the configuration change:
4

Check Gateway status

Confirm the Gateway is running:

​
Configure OpenClaw in EnConvo

Open EnConvo Settings -> AI Model -> OpenClaw, then configure the credential provider. OpenClaw credential settings in EnConvo EnConvo uses the Chat Completions API for OpenClaw automatically.
Use the base URL ending in /v1, not the full /v1/chat/completions endpoint. For example, if your endpoint is http://192.168.1.18:18789/v1/chat/completions, enter http://192.168.1.18:18789/v1.
To read the Gateway token from the default OpenClaw config file:
EnConvo sends this value as:
Click Validate after entering the base URL and token.

​
API Behavior and Attachments

EnConvo sends OpenClaw requests through OpenAI-compatible Chat Completions:
Use openclaw:main or another model name advertised by your OpenClaw agent list.
Image attachments are not sent to OpenClaw by EnConvo. Treat the OpenClaw provider as a text/chat provider in EnConvo. For image workflows, use a vision-capable model provider or run OCR/image analysis before sending text to OpenClaw.

​
Use OpenClaw as an AI Model

Once configured, OpenClaw appears in the model selector. Choose OpenClaw and select the agent-backed model, such as openclaw:main. OpenClaw selected as the chat model Use this mode when you want an EnConvo conversation, command, or feature to run through an OpenClaw agent while keeping the normal EnConvo interface.
1

Open the model picker

In chat or another model-powered EnConvo feature, click the current model name.
2

Choose OpenClaw

Select OpenClaw in the provider list.OpenClaw in the model selector
3

Select an OpenClaw agent model

Choose openclaw:main or another OpenClaw agent from the model list.
4

Run the feature normally

Ask your question or run the EnConvo feature. The selected OpenClaw agent handles the model call behind the scenes.
EnConvo loads OpenClaw models from openclaw agents list. If the OpenClaw CLI is not available locally, EnConvo falls back to openclaw:main.

​
Create an EnConvo Agent for OpenClaw

You can also create an EnConvo agent that coordinates an OpenClaw agent. This is useful when you want an EnConvo-facing workflow, tool set, or prompt around a specific OpenClaw agent.
1

Open Create Agent

Open SmartBar and search for Create Agent.Create Agent command in EnConvo
2

Name the agent

Create a clear title, such as OpenClaw Main.Create New Agent form for OpenClaw
3

Write coordinator instructions

Give the EnConvo agent instructions that explain how it should work with OpenClaw.
4

Choose the OpenClaw model

In the agent’s model settings, select OpenClaw and choose openclaw:main.
5

Save and use the agent

Start a conversation with the new EnConvo agent. It will use the selected OpenClaw agent model while retaining the EnConvo agent interface and tools you configured.

​
Troubleshooting

Make sure the OpenClaw provider is enabled in Settings -> AI Model. If the model list is empty, verify that openclaw agents list works locally or use the default openclaw:main.
Recheck the Gateway token. EnConvo expects the value from gateway.auth.token and sends it as a Bearer token.
Confirm the Gateway is running with openclaw gateway status. If EnConvo is on another device, set gateway.bind to lan, restart the Gateway, and use the host’s LAN IP in the base URL.
OpenClaw can report that the LaunchAgent restarted before the HTTP Gateway is ready. Wait a few seconds and check the setup card’s runtime badge again. You can also verify directly with openclaw gateway status and curl http://127.0.0.1:18789/health.
Make sure EnConvo is using the same token as gateway.auth.token in ~/.openclaw/openclaw.json. The setup status can still detect a running Gateway through /health, but model validation requires the bearer token.
The OpenClaw provider in EnConvo is currently text-only. EnConvo will not send image attachments to OpenClaw; choose a vision-capable provider for direct image input.
Enter http://<gateway-host>:<port>/v1. Do not include /chat/completions in the EnConvo base URL field.