Related:

- Multi-agent routing: [Multi-Agent Routing](/concepts/multi-agent)

- Agent workspace: [Agent workspace](/concepts/agent-workspace)

- Skill visibility config: [Skills config](/tools/skills-config)

- [Multi-agent routing](/concepts/multi-agent)

- [Agent workspace](/concepts/agent-workspace)

- [Skills config](/tools/skills-config): skill visibility configuration.

## Examples

Use routing bindings to pin inbound channel traffic to a specific agent.

If you also want different visible skills per agent, configure

`agents.defaults.skills` and `agents.list[].skills` in `openclaw.json`. See

[Skills config](/tools/skills-config) and

[Configuration Reference](/gateway/config-agents#agents-defaults-skills).

If you also want different visible skills per agent, configure `agents.defaults.skills` and `agents.list[].skills` in `openclaw.json`. See [Skills config](/tools/skills-config) and [Configuration reference](/gateway/config-agents#agents-defaults-skills).

List bindings:

Related docs:

- Channel guides: [Channels](/channels/index)

- Channel guides: [Channels](/channels)

- Gateway configuration: [Configuration](/gateway/configuration)

## Common commands

openclaw channels remove --channel telegram --delete

```

Tip: `openclaw channels add --help` shows per-channel flags (token, private key, app token, signal-cli paths, etc).

<Tip>

`openclaw channels add --help` shows per-channel flags (token, private key, app token, signal-cli paths, etc).

</Tip>

Common non-interactive add surfaces include:

If your config was already in a mixed state (named accounts present and top-level single-account values still set), run `openclaw doctor --fix` to move account-scoped values into the promoted account chosen for that channel. Most channels promote into `accounts.default`; Matrix can preserve an existing named/default target instead.

## Login / logout (interactive)

## Login and logout (interactive)

```bash

openclaw channels login --channel whatsapp

openclaw channels logout --channel whatsapp

```

Notes:

- `channels login` supports `--verbose`.

- `channels login` / `logout` can infer the channel when only one supported login target is configured.

- `channels login` and `logout` can infer the channel when only one supported login target is configured.

## Troubleshooting

Interactive prompt to set up credentials, devices, and agent defaults.

Note: The **Model** section now includes a multi-select for the

`agents.defaults.models` allowlist (what shows up in `/model` and the model picker).

Provider-scoped setup choices merge their selected models into the existing

allowlist instead of replacing unrelated providers already in the config.

Re-running provider auth from configure preserves an existing

`agents.defaults.model.primary`; use `openclaw models auth login --provider <id> --set-default`

or `openclaw models set <model>` when you intentionally want to change the default model.

When configure starts from a provider auth choice, the default-model and

allowlist pickers prefer that provider automatically. For paired providers such

as Volcengine/BytePlus, the same preference also matches their coding-plan

variants (`volcengine-plan/*`, `byteplus-plan/*`). If the preferred-provider

filter would produce an empty list, configure falls back to the unfiltered

catalog instead of showing a blank picker.

Tip: `openclaw config` without a subcommand opens the same wizard. Use

`openclaw config get|set|unset` for non-interactive edits.

<Note>

The **Model** section includes a multi-select for the `agents.defaults.models` allowlist (what shows up in `/model` and the model picker). Provider-scoped setup choices merge their selected models into the existing allowlist instead of replacing unrelated providers already in the config. Re-running provider auth from configure preserves an existing `agents.defaults.model.primary`. Use `openclaw models auth login --provider <id> --set-default` or `openclaw models set <model>` when you intentionally want to change the default model.

</Note>

When configure starts from a provider auth choice, the default-model and allowlist pickers prefer that provider automatically. For paired providers such as Volcengine and BytePlus, the same preference also matches their coding-plan variants (`volcengine-plan/*`, `byteplus-plan/*`). If the preferred-provider filter would produce an empty list, configure falls back to the unfiltered catalog instead of showing a blank picker.

<Tip>

`openclaw config` without a subcommand opens the same wizard. Use `openclaw config get|set|unset` for non-interactive edits.

</Tip>

For web search, `openclaw configure --section web` lets you choose a provider

and configure its credentials. Some providers also show provider-specific

request and exits; rerun approval with the exact request ID after verifying

the details.

Note: if a device retries pairing with changed auth details (role/scopes/public

key), OpenClaw supersedes the previous pending entry and issues a new

`requestId`. Run `openclaw devices list` right before approval to use the

current ID.

<Note>

If a device retries pairing with changed auth details (role, scopes, or public key), OpenClaw supersedes the previous pending entry and issues a new `requestId`. Run `openclaw devices list` right before approval to use the current ID.

</Note>

If the device is already paired and asks for broader scopes or a broader role,

OpenClaw keeps the existing approval in place and creates a new pending upgrade

- `--timeout <ms>`: RPC timeout.

- `--json`: JSON output (recommended for scripting).

Note: when you set `--url`, the CLI does not fall back to config or environment credentials.

Pass `--token` or `--password` explicitly. Missing explicit credentials is an error.

<Warning>

When you set `--url`, the CLI does not fall back to config or environment credentials. Pass `--token` or `--password` explicitly. Missing explicit credentials is an error.

</Warning>

## Notes

stale removed-provider default.

- `models status` may show `marker(<value>)` in auth output for non-secret placeholders (for example `OPENAI_API_KEY`, `secretref-managed`, `minimax-oauth`, `oauth:chutes`, `ollama-local`) instead of masking them as secrets.

### `models scan`

### Models scan

`models scan` reads OpenRouter's public `:free` catalog and ranks candidates for

fallback use. The catalog itself is public, so metadata-only scans do not need

`--set-default` and `--set-image` require live probes; metadata-only scan

results are informational and are not applied to config.

### `models status`

### Models status

Options: