APIrove

Home / API docs / CC Switch + ChatGPT desktop

BEGINNER · DESKTOP APP

Use CC Switch and ChatGPT desktop with APIrove

CC Switch is installed on the computer, ChatGPT or Codex is the desktop app, and the key is from APIrove. Finish the steps, then test with a new chat.

Beginner guide · about 5 minutes. Updated 2026-11-06. The screenshots show the Chinese CC Switch interface.

What this page is for

  1. Turn on “统一 Codex 会话历史” (Unify Codex conversation history). The switch should be orange.
  2. After you change providers: fully quit the desktop app, then turn that switch off and on again, then reopen the app. Do not toggle first and quit afterwards.
  3. Decide whether a missing chat, a continuation error, 429, or 502 is something you fix or something you send to us.
One sentence: turning the switch on does not mean an old chat can continue on a different provider. If it will not continue, start a new chat. The old text is not deleted.

What you need

  • CC Switch on the computer, a version that includes unified Codex history.
  • ChatGPT or Codex desktop, the window you type in.
  • An APIrove key and base URL https://apirove.com/v1. The key on this page is a placeholder. Do not post a real key.
  • Use the text group (APIrove-Text) for chat and images. Use the full group (APIrove-Unified) when you need Claude.

If you only need the address and key, start with the 3-step setup. This page is about desktop history and errors.

Recommended setup, in order

  1. 1

    In CC Switch, switch to the provider you will use

    Base URL https://apirove.com/v1 and your own key. After you save, that row says In use.

  2. 2

    Fully quit ChatGPT or Codex

    End the process. Closing the window is not enough. On macOS use Quit. On Windows quit from the tray or end it in Task Manager.

  3. 3

    Back in CC Switch, turn unified history off, then on

    Do this even when it is already orange. If a dialog asks about importing existing official sessions, choose what you need. Stay in CC Switch. Do not open the desktop app yet.

  4. 4

    Then reopen the desktop app

    Open it only after the off-then-on toggle. Do not restart halfway, and do not toggle before you quit.

  5. 5

    Start a new chat

    Do not continue the old chat. Send one short sentence, then start the real work.

1. Turn on unified Codex history

The switch makes history from the official login and from a third-party provider easier to see in one list. CC Switch 4.0.7 says the switch is optional if you only use a new desktop build. If you use APIrove and you switch providers, leave it on.

CC Switch app settings in Chinese. Red labels mark App config in the sidebar and the orange Unify Codex conversation history switch.
Open App config, then Codex, then turn on 统一 Codex 会话历史. The blue note says the list can come together after a provider switch. The red note says continuing an old chat across providers can still fail: start a new chat.
Close-up of Codex settings. A callout says to turn the switch on, and a red box surrounds the orange Unify Codex conversation history toggle.
The switch has to be orange. The callout says to turn this switch on.
The Codex section of CC Switch app settings outlined in red, with the unified history switch also outlined and turned on.
The whole Codex block is on this page. The row inside the inner red box is the history switch.
Unmarked CC Switch app settings. Under Codex, Unify Codex conversation history is switched on.
The same screen without boxes, so you can match the row. It is the second row under Codex.

CC Switch’s own write-up of the switch is here (we are not copying it): unified Codex session history. Quit the app and handle errors the way this page says.

2. Base URL and key

  1. Create or select a provider in CC Switch. Name it so you can tell it is APIrove.
  2. Set the base URL below. Paste your own key from API keys. Do not use the placeholder.
  3. Save. That row must say In use.
Base URL
https://apirove.com/v1
Placeholder only. Use your own key.
YOUR_API_KEY
CC Switch Codex provider list with names and addresses covered. The active row shows In use, and a toast says to restart the client.
Look for In use and the toast: Switched successfully. Restart the client to apply changes. Provider names and addresses in this picture are covered.

3. After you quit: turn unified history off, then on

Leaving the switch on is not enough, and do not toggle it before you quit. After you change providers, including a switch between two relays: fully quit the desktop app first, then go back to CC Switch and turn “统一 Codex 会话历史” off and back on, and only then reopen the app. The toggle sits between quit and reopen. Start a new chat last.
  1. In CC Switch, select the APIrove provider and confirm In use.
  2. Fully quit ChatGPT or Codex. End the process. On macOS use Quit. On Windows quit from the tray or end the process in Task Manager.
  3. Back in CC Switch → App config → Codex, turn unified history off, then on. If asked about importing existing official sessions, choose what you need.
  4. Open the desktop app again.
  5. Start a new chat and send one short sentence. Do not continue the old chat.
A fresh Codex desktop window after a full relaunch, with an empty new-chat prompt.
After you quit and reopen, you should land on a blank chat. Start there. Do not reopen an old item in the sidebar for the test.
Codex desktop answered a new chat successfully and showed a red star.
A successful test looks like a normal reply in a new chat. Then start the real work.

Day to day

  • After a provider or key change: fully quit, then toggle off and on, then reopen, test a new chat, then work.
  • Do not switch providers in the middle of a long chat and expect it to continue.
  • One shared list does not mean an old chat can always continue. Start a new chat, or paste the plain text again. The record was not deleted.

Three problems that are not the same

  • The list: the switch puts history in one list. If the list is stale right after a switch: fully quit first, then toggle off and on, then reopen the desktop app.
  • An old chat will not continue: encrypted content from the old session often cannot be read by the other provider. The data is still there. Start a new chat and paste the plain text if you need it.
  • opaque: Cannot prove ownership of opaque conversation state or CLIENT_TOOL_CONTINUATION_UNAVAILABLE means this turn cannot continue. Start a new chat. You usually do not change the key. That is not the same fault as a list that did not merge, but the first action is the same: a new chat.

Troubleshooting

Choose the one you see.

The old chat is not in the list
  • Turn unified history on and check that it is orange.
  • Or switch back to the provider you used then, and look again.
  • If you just switched: fully quit first, then toggle off and on, then reopen.

If it is still missing, use the backup path in the CC Switch guide on your own computer, or write to us with a screenshot.

The old chat will not continue, or you see opaque
  • Cannot prove ownership of opaque conversation state
  • CLIENT_TOOL_CONTINUATION_UNAVAILABLE

This turn cannot continue. Start a new chat. Paste the plain text if you need the old content. If you just switched providers: fully quit, then toggle unified history off and on, then reopen. Do not toggle before you quit. You usually do not need a new key.

If a brand-new chat fails with the same sentence immediately, write to us with the screenshot and the approximate time.

Error text Cannot prove ownership of opaque conversation state, underlined in red, telling you to start a new conversation or resend the plain text.
When you see this sentence, start a new chat or paste the full plain text again.
The same opaque error sentence in a dark chat window, underlined in red.
The same sentence in a dark window. The rest of the customer chat is not shown.
You just switched providers and the list or the old chat is wrong
  1. Confirm the provider you want says In use.
  2. Fully quit the desktop app.
  3. Back in CC Switch, turn unified history off, then on.
  4. Reopen the desktop app.
  5. Start a new chat. Do not continue the old one.

If the new chat immediately shows opaque, use the opaque steps above and then write to us.

401 or 403

401: the key is wrong or missing. Paste it again in CC Switch, save the provider, and fully quit the desktop app.

403: this key cannot use that model. For a model that is not in the text group (such as Claude), use a full-group key and start a new chat.

429

Wait a few minutes and run fewer requests at once. If 429 keeps going, write to us.

400, other than opaque

Start a new chat, send one short sentence, and check the model name. If it still fails, send the full error text.

502 or 503

Wait 1–2 minutes and retry, or start a new chat. If it is still down after about 10 minutes, write to us with the time and any request id.

413

The request is too large. Shorten the context, attach less, and start a smaller chat. If 413 remains, ask us about the limit.

Image generation failed, or the model is not in this group

Text-group and full-group keys can both generate images; check that image generation is not turned off for the key. The model id has to match the model directory. Try a short prompt in a new chat.

Codex desktop showing a 404 that the model is not supported by any configured account in this group. The address and request id are covered.
This says the current key’s group does not include that model. Check the group and the model name. The address and request id are covered.
Insufficient balance

A low balance is not a stuck conversation. A new chat does not add credit. Open the console and follow what it shows. For balance questions, write to help@apirove.com.

Error table

Cannot continue → new chat. Bad key → check the key. Too fast → wait. Still down → write to us.

Do the middle column first. Use the last column only if that did not work.
What you see Meaning Do this first If it is still broken
Cannot prove ownership of opaque conversation state / CLIENT_TOOL_CONTINUATION_UNAVAILABLE This turn cannot continue New chat Paste plain text if you need it. After a switch: fully quit, then toggle off and on, then reopen Same error on a brand-new chat → write to us with a screenshot and the time
401 Key missing or wrong Check key Paste again, save, restart the desktop app Ask us to check the key. Do not email the whole key
403 No permission, or wrong group Check group Check images are on for the key. Start a new chat Ask us to check the group
429 Too fast, or the limit is tight Wait Slow down for a few minutes If it continues, write to us
400 (other) Format or parameter New chat Send a short sentence and check the model name Send the full error
502 / 503 Busy or briefly unavailable Retry Wait 1–2 minutes, or start a new chat Still down after about 10 minutes → write to us
413 Too large Shorten the context and start a smaller chat Ask us about the limit
Insufficient balance Not enough credit. Unrelated to the chat state Check the balance in the console. A new chat will not fix it Write to us about balance questions
Old chat missing from the list It is probably under another provider Turn the switch on, or switch back. After a change: fully quit, then toggle off and on, then reopen Check the local backup path, or write to us

When to handle it yourself, and when to write

Handle it yourself: a new chat, a key check, a short wait, a smaller request. After a provider switch, use the five steps: fully quit, then toggle off and on, then reopen.

Write to us: a brand-new chat fails with the same error immediately; 401 or 403 remains after you recheck the key; 429 does not stop; 502 or 503 lasts about 10 minutes; the balance does not match what you expect.

  1. A screenshot of the full error.
  2. The approximate time, with your time zone.
  3. Whether you already fully quit, then toggled the switch off and on, reopened the app, and started a new chat.

Keys: API keys. Model names: models. Longer setup notes: pro guide.