Skip to main content
OpenClaw connects an AI assistant to chat interfaces through its Gateway. This guide uses OpenClaw 2026.10.5 to set up AIHubMix models.

Install

OpenClaw requires Node.js 24.16+ on the 24.x line, or 26.1+. Node.js 25 is unsupported. Node.js 26 is recommended. The official installer provisions a compatible Node.js when needed and starts onboarding. macOS, Linux, or WSL2:
Windows PowerShell:
If you manage Node.js yourself, you can use npm. With npm 12 or 11.16+:
Omit --allow-scripts=openclaw on npm 11.15 or earlier. If the installer has already started onboarding, do not run openclaw onboard again.

First-time setup

On a fresh install, read the security notice in openclaw onboard, choose Quick start, then One agent. At the model connection picker, choose Skip for now. OpenClaw prepares the workspace and local Gateway configuration, then exits. Neither an AI connection nor the Gateway is running yet. Continue with one of the AIHubMix methods below.
OpenClaw onboarding with Quick start selectedOpenClaw onboarding with One agent selectedOpenClaw model connection list with Skip for now at the bottom
AIHubMix is not in the built-in provider list. To configure it within the wizard, choose More… → Custom Provider and enter https://aihubmix.com/v1, your AIHubMix API key, OpenAI-compatible, and an available model ID. The wizard verifies a real response before saving the connection and starting a foreground Gateway.

Configure AIHubMix

Method 1: Plugin

aihubmix-auth is a third-party plugin. Review the npm source and capability prompts before confirming trust and permissions. These steps assume that the Gateway is still stopped after first-time setup.
After installation, run the authentication command and enter your AIHubMix API key at the prompt. You do not need to put the key in a command or document. Run the command with --set-default while the Gateway is stopped.
The plugin provides four model groups: aihubmix-openai, aihubmix-anthropic, aihubmix-google, and aihubmix-other. After authenticating once, select a model available to your account. For example:
To select another OpenAI-compatible model, use its actual model ID:
Model availability depends on the AIHubMix model catalog and your account access.

Method 2: Edit the configuration file

Without the plugin, add a custom provider to ~/.openclaw/openclaw.json. First, make AIHUBMIX_API_KEY available to the process running the Gateway. This example includes only the fields needed here. Merge it into an existing configuration instead of overwriting other settings. On macOS, Linux, or WSL2, set the variable in the same terminal that will run the Gateway. Replace the placeholder with your own key:
On Windows PowerShell:
These commands apply only to the current terminal session. Set the variable again after opening a new terminal.
The model context and output limits come from the gpt-6-sol model page. For a background Gateway service, make sure its process can also read AIHUBMIX_API_KEY; environment variables in your current terminal are not automatically passed to an installed service. See OpenClaw secrets management for service credentials.

Test and start

With a valid key, test a model request. A model reply confirms that the connection works:
Start the Gateway in the foreground, then open the dashboard from another terminal:
openclaw gateway keeps its terminal occupied. Press Ctrl+C there to stop it. To use a background service, stop the foreground process and run openclaw gateway install.

Troubleshooting

Command not found

Check that installation completed and that the global npm directory is on your PATH:
On Windows, add the output directory to the system PATH. On macOS and Linux, see the OpenClaw Node.js installation guide.

Update the plugin or OpenClaw

Stop the Gateway before updating the plugin. Press Ctrl+C for a foreground Gateway, or run openclaw gateway stop for an installed service. Then:
Run openclaw gateway start for an installed service, or openclaw gateway for foreground use. To update OpenClaw itself, run openclaw update. A manually started foreground Gateway must be restarted manually.

Gateway port is in use

Stop the existing foreground Gateway or use openclaw gateway stop for an installed service before starting the desired instance. openclaw gateway start does not install a missing service.

Resources

Updated: 2026-10-20