#OpenClaw Telegram stuck on ChatGPT OAuth usage limit – how to switch to API?

1 messages · Page 1 of 1 (latest)

prime field
#

Hey all — quick question about OpenClaw + Telegram auth.

Problem:
My Telegram bot keeps replying:

“You have hit your ChatGPT usage limit (plus plan)”

So Telegram is clearly using ChatGPT OAuth, hitting the Plus quota, even though I do have OpenAI API credits available.

What I want to do:

  1. Switch now to OpenAI API key (pay-as-you-go) so Telegram stops hitting Plus limits
  2. Be able to switch back later to OAuth/Auth if needed

Question:
What’s the correct / canonical way to force the Telegram channel to use the OpenAI API provider instead of OAuth, and then switch back cleanly later?

Is this controlled via:

  • ⁨auth-profiles.json⁩?
  • a specific env file (⁨~/.openclaw/.env⁩) since the gateway runs as a service?
  • a channel-level provider setting?

Any guidance appreciated 🙏

patent dust
#

i do just configure api key, enable models and say in chat which model to use

prime field
# patent dust i do just configure api key, enable models and say in chat which model to use

Thanks. Just to clarify:

Saying which model to use in chat only works after the provider is already set to OpenAI API.
Right now Telegram is still using ChatGPT OAuth, so changing the model in chat doesn’t prevent the Plus usage limit.

What I’m missing is the explicit step to switch the Telegram channel’s provider from OAuth → OpenAI API (and how to switch it back later).

Where is that provider actually defined?

patent dust
#

open the config path

#

and adjust the default model ig

prime field
#

Thanks a lot for the help 🙏
You were right — setting the default model via openclaw models / config was the missing piece.
Once I switched the primary model to the OpenAI API one, everything worked perfectly.

Appreciate it!