Get Started with openclaw configure

I have spent too much time staring at empty configuration files, trying to remember the exact key names for API credentials or hunting down specific channel IDs. It is easy to miss a required field or mess up the formatting when you edit config files by hand.

I prefer using the interactive wizard. It walks you through the setup so you don’t have to guess what comes next.

What You’ll Need

• The openclaw CLI installed on your machine.
• Access to your terminal.

Quick Start

The fastest way to get your environment ready is to use the interactive prompt. I recommend following these steps:

1. Run the wizard: Open your terminal and type openclaw configure. You can also use openclaw config to start the same process.
2. Select your models: When you reach the Model section, use the multi-select tool to choose which models appear in your agents.defaults.models allowlist. This controls what you see in the model picker.
3. Set up your Gateway: Choose where your Gateway runs. This action automatically updates your gateway.mode setting.
4. Target specific areas: If you don’t want to go through everything, use flags to jump to specific sections. For example:

openclaw configure --section models --section channels

If you prefer to make quick edits without the interactive UI, you can use openclaw config get, set, or unset for direct changes.

Troubleshooting

Problem: I don’t know the specific IDs for my Slack or Discord channels.

When you set up channel-oriented services like Slack, Discord, Matrix, or Microsoft Teams, the wizard asks for allowlists. You do not need to hunt for IDs manually. You can enter the channel names, and the wizard resolves those names to IDs for you.

Problem: I only need to change where the Gateway runs.

You can select “Continue” through the wizard without changing other sections. Selecting the Gateway location will still update your gateway.mode as expected.

结尾

If you run into issues while setting up your environment, check out the AI Setup Assistant.

What’s Next

• Gateway configuration reference
• Config CLI