#Something went wrong while processing your request. Please try again, or use /new to start a fresh

14 messages · Page 1 of 1 (latest)

finite peak
#

I am using open ai - gpt 5.4. Suddenly started last night. I think I need to reconnect to to my chat GPT account (Subscription)? Had been working fine for 8 days.

icy sundialBOT
tired jacinthBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

icy sundialBOT
grand impBOT
#

If you’re using openai/gpt-5.4, then probably not your ChatGPT subscription.

In OpenClaw those are two different auth routes:

  • openai/gpt-5.4 = OpenAI API key
  • openai-codex/gpt-5.4 = ChatGPT/Codex sign-in

So a ChatGPT reconnect only helps if you’re actually on openai-codex/*.

First, can you paste:

openclaw --version
openclaw status --all
openclaw models status
#

A couple quick checks meanwhile:

  • If your model is openai-codex/gpt-5.4, re-login with:
    openclaw models auth login --provider openai-codex
  • If your model is openai/gpt-5.4, check the gateway still has a valid OPENAI_API_KEY and that billing/quota is okay.
  • If the error is the generic “Something went wrong…” thread title, sometimes the session got out of sync, and /new fixes it.

Docs:

Paste those outputs and I’ll help narrow it down. 🦐

finite peak
#

Agents
┌─────────────────┬────────────────┬──────────┬──────────┬─────────────────────────────────────────────────────┐
│ Agent │ Bootstrap file │ Sessions │ Active │ Store │
├─────────────────┼────────────────┼──────────┼──────────┼─────────────────────────────────────────────────────┤
│ main │ ABSENT │ 148 │ 9m ago │ ~/.openclaw/agents/main/sessions/sessions.json │

grand impBOT
#

That Agents block only shows the session store, not the OpenAI auth state.

So from this alone, I would not assume you need to reconnect ChatGPT.

If your model is really openai/gpt-5.4, then ChatGPT subscription auth is not the path anyway, that route uses an OpenAI API key. ChatGPT/Codex sign-in is only for openai-codex/gpt-5.4.

Best next checks:

  1. Try /new first
    If the new session works, the old one likely just got out of sync.

  2. Paste these:

    openclaw --version
openclaw models status
#

  1. If models status shows openai-codex/*, re-login:

    openclaw models auth login --provider openai-codex

  2. If it shows openai/*, check your OPENAI_API_KEY / OpenAI Platform billing, not ChatGPT subscription.

Relevant docs:

If you paste openclaw models status, I can usually tell pretty quickly which side this is. 🦐

finite peak
#

OpenClaw 2026.4.11 (769908e)

grand impBOT
#

Nice, that version is recent, so this does not look like one of the older known session-store bugs.

At this point I’d check auth vs session:

  1. Run:

    openclaw models status

    and paste it here.

  2. Also try:

    /new

    in chat.

Interpretation:

#
  • If /new works, it was probably a stale/out-of-sync session, not your subscription.
  • If /new still fails and models status shows openai/*, check OpenAI API key / platform billing.
  • If models status shows openai-codex/*, then a Codex/ChatGPT re-login may be the fix.

So, version looks okay. The next useful thing is definitely openclaw models status.

finite peak
#

Looks like I hit my weekly usage limit, but I didnt think that was possible on the GPT 5.4 pro plan subscription?

Weekly usage limit

0%
remaining

grand impBOT
#

Ah, yep, that explains it.

If you’re on openai-codex/gpt-5.4, then yes, hitting a weekly usage limit is possible. Those quota windows are OpenAI-managed and plan-dependent, and they can differ from the normal ChatGPT web/app experience.

So in this case:

  • Reconnecting won’t reset it
  • It’s probably not an OpenClaw bug
  • You likely need to either:
    1. wait for the quota window to reset, or
    2. switch to openai/gpt-5.4 with an OpenAI API key instead of subscription OAuth

That split is documented here:

In short: