[Bug] Models configured via OAuth not being pulled by ClawPanel

[adam479]

Bug Description

ClawPanel is not fetching or displaying models that have been configured through OAuth authentication. The model list appears empty or stale even after a successful OAuth login/authorization flow.

Steps to Reproduce

1. Configure a model provider using OAuth.
2. Complete the OAuth authorization flow successfully.
3. Navigate to the model selection / model list in ClawPanel.
4. Observe that the models configured via OAuth are not listed or pulled.

Expected Behavior

After a successful OAuth authorization, ClawPanel should automatically fetch and display all models available under the authenticated OAuth provider/account.

Actual Behavior

Models configured through OAuth are not being pulled. The model list is empty or only shows models configured via API key — OAuth-authenticated models are missing.

Environment

• ClawPanel Version: [e.g., latest / vX.X.X]
• Browser: [e.g., Chrome 123]
• OS: [e.g., Windows 11 / macOS / Linux]

Additional Context

• This may be related to how the Auth Manager injects OAuth tokens vs. API keys when fetching the model list.
• Possible cause: OAuth token may not be passed in the request headers when the model discovery/pull endpoint is called.
• Workaround (if any): None found so far.

Logs / Screenshots

[1186258278]

Hi, thanks for reporting this!

This is a known architectural limitation: ClawPanel reads model configurations from openclaw.json's models.providers section, which stores API key-based provider configs. Models configured through OAuth are managed dynamically by OpenClaw's Auth Manager at runtime and are not written to openclaw.json.

Current status:

• API key providers: fully supported in ClawPanel (add/edit/test/sync)
• OAuth providers: visible in OpenClaw's native Control UI, but not yet surfaced in ClawPanel

Workaround:
You can access OAuth-configured models through OpenClaw's built-in Control UI (Dashboard → Control UI card → click to open in browser).

We're tracking this as a feature gap and will evaluate adding OAuth provider visibility in a future release. Thanks for your patience!