5 replies

Multi-Agent Routing Breaks When Adding Custom Provider

Environment: OpenClaw 2026.2.9, macOS, 3-agent setup, Telegram

Issue

Adding a custom model provider (MLX) breaks agent routing. Messages to specific agents get routed to main agent instead.

Working Config

{
  "agents": {
    "list": [
      { "id": "main" },
      { "id": "mint", "workspace": "/mint", "model": "anthropic/claude-sonnet-4-5" }
    ]
  },
  "bindings": [
    { "agentId": "main", "match": { "accountId": "main_bot" }},
    { "agentId": "mint", "match": { "accountId": "mint_bot" }}
  ]
}

{
  "agents": {
    "list": [
      { "id": "main" },
      { "id": "mint", "workspace": "/mint", "model": "anthropic/claude-sonnet-4-5" }
    ]
  },
  "bindings": [
    { "agentId": "main", "match": { "accountId": "main_bot" }},
    { "agentId": "mint", "match": { "accountId": "mint_bot" }}
  ]
}

Both agents work correctly

Broken Config

{
  "models": { "providers": { "mlx": { "baseUrl": "http://127.0.0.1:1234/v1", "apiKey": "mlx-local", "api": "openai-completions" }}},
  "agents": { "list": [
    { "id": "main" },
    { "id": "mint", "workspace": "/mint", "model": "mlx/typhoon2-model" }
  ]}
}

{
  "models": { "providers": { "mlx": { "baseUrl": "http://127.0.0.1:1234/v1", "apiKey": "mlx-local", "api": "openai-completions" }}},
  "agents": { "list": [
    { "id": "main" },
    { "id": "mint", "workspace": "/mint", "model": "mlx/typhoon2-model" }
  ]}
}

Mint messages go to main agent

Symptoms

sessions_list

sessions_list

only shows

agent:main:main

agent:main:main

(no

agent:mint:*

agent:mint:*

)
- Messages to

@mint_bot

@mint_bot

→ routed to main
- Mint uses main agent's identity
- Log:

inherited auth-profiles from main agent

inherited auth-profiles from main agent

Reproduce

1. Working multi-agent (same provider)
2. Add custom provider to

models.providers

models.providers

3. Change agent to use new provider
4. Message affected agent → gets wrong response

Workaround

Remove custom provider, revert to original model →

works

Question

Is this a known issue? Any guidance for multi-agent + custom providers?

Thanks!

nynat@nynats

FotC�

Friends of the Crustacean 🦞🤝•4h ago•

5 replies

^nnnynnn^

Multi-Agent Routing Breaks When Adding Custom Provider

Environment: OpenClaw 2026.2.9, macOS, 3-agent setup, Telegram

Issue

Adding a custom model provider (MLX) breaks agent routing. Messages to specific agents get routed to main agent instead.

Working Config

{
  "agents": {
    "list": [
      { "id": "main" },
      { "id": "mint", "workspace": "/mint", "model": "anthropic/claude-sonnet-4-5" }
    ]
  },
  "bindings": [
    { "agentId": "main", "match": { "accountId": "main_bot" }},
    { "agentId": "mint", "match": { "accountId": "mint_bot" }}
  ]
}

{
  "agents": {
    "list": [
      { "id": "main" },
      { "id": "mint", "workspace": "/mint", "model": "anthropic/claude-sonnet-4-5" }
    ]
  },
  "bindings": [
    { "agentId": "main", "match": { "accountId": "main_bot" }},
    { "agentId": "mint", "match": { "accountId": "mint_bot" }}
  ]
}

Both agents work correctly

Broken Config

{
  "models": { "providers": { "mlx": { "baseUrl": "http://127.0.0.1:1234/v1", "apiKey": "mlx-local", "api": "openai-completions" }}},
  "agents": { "list": [
    { "id": "main" },
    { "id": "mint", "workspace": "/mint", "model": "mlx/typhoon2-model" }
  ]}
}

{
  "models": { "providers": { "mlx": { "baseUrl": "http://127.0.0.1:1234/v1", "apiKey": "mlx-local", "api": "openai-completions" }}},
  "agents": { "list": [
    { "id": "main" },
    { "id": "mint", "workspace": "/mint", "model": "mlx/typhoon2-model" }
  ]}
}

Mint messages go to main agent

Symptoms

sessions_list

sessions_list

only shows

agent:main:main

agent:main:main

(no

agent:mint:*

agent:mint:*

)
- Messages to

@mint_bot

@mint_bot

→ routed to main
- Mint uses main agent's identity
- Log:

inherited auth-profiles from main agent

inherited auth-profiles from main agent

Reproduce

1. Working multi-agent (same provider)
2. Add custom provider to

models.providers

models.providers

3. Change agent to use new provider
4. Message affected agent → gets wrong response

Workaround

Remove custom provider, revert to original model →

works

Question

Is this a known issue? Any guidance for multi-agent + custom providers?

Thanks!

nynat@nynats

Multi-Agent Routing Breaks When Adding Custom Provider

Issue

Working Config

Broken Config

Symptoms

Reproduce

Workaround

Question

Similar Threads

Multi-Agent Routing Breaks When Adding Custom Provider

Issue

Working Config

Broken Config

Symptoms

Reproduce

Workaround

Question

Similar Threads

Similar Threads

Similar Threads