Two: Gemini CLI + Codex Hands-on

In the previous article, we successfully converted Qwen Code into an API and called it in Cherry Studio through a simple configuration on CLIProxyAPI. I believe that by reading this, you have a preliminary understanding of the powerful functions and convenience of this tool.

In this tutorial, we will continue to explore and integrate Codex and Gemini CLI.

It should be noted that the configuration file used in this operation is the same as the one in the previous Qwen tutorial.

yaml

port: 8317

# Please fill in the folder location according to your actual situation
auth-dir: "Z:\\CLIProxyAPI\\auths"

request-retry: 3

quota-exceeded:
  switch-project: true
  switch-preview-model: true

api-keys:
# Please set the Key yourself, used for client access to the proxy
- "ABC-123456"

Configure Codex

First, let's configure Codex. The OAuth authorization process for Codex is very similar to the previous Qwen. Enter cli-proxy-api --codex-login in the terminal command line, and the system will automatically open the ChatGPT authorization page. Please log in with your ChatGPT account.

If it is a ChatGPT Team account, you need to select the corresponding workspace. The page for successful authorization is as follows:

Back in the terminal command line, you can see that the authentication file has been successfully generated and saved.

If you have multiple ChatGPT accounts, just repeat the same operation a few times.

It should be noted that currently Codex can only be used by paid ChatGPT members, and free users do not have permission.

Configure Gemini CLI

Next, let's add Gemini CLI. Gemini CLI is completely free, but some users may encounter problems during the configuration process. Therefore, here I will take you through the entire authorization and authentication process step by step, starting from creating a Google Cloud project.

First, please log in to https://console.cloud.google.com/ with your Google account. After successful login, click the position shown in the figure:

Click "New Project".

After naming the project, click "Create".

According to the position in the first step, select the project you just created.

First, copy the project ID in the red box for later use, and then click the position indicated by the arrow in the upper left corner.

Click "APIs & Services" -> "Enabled APIs & services" in order.

Click "ENABLE APIS AND SERVICES".

Enter cloudaicompanion.googleapis.com in the search box shown in the figure, and then click the searched "Gemini for Google Cloud".

Click "Enable".

So far, all the preliminary preparations for Google Cloud have been completed. Now, let's go back to the directory where the CLIProxyAPI program is located, open the terminal command line, and enter cli-proxy-api --login --project_id [your project ID]. For example, in this case, it is cli-proxy-api --login --project_id mimetic-planet-473413-v7.

Then the authorization page will pop up. Please log in with the Google account that you just used for preparation.

The page for successful verification is as follows:

Back in the terminal command line, you can see that the authentication file has been successfully saved.

Some readers may be curious why the command line information after successful verification of Codex and Gemini CLI is different from that of Qwen. The answer is that when verifying Codex and Gemini CLI, CLIProxyAPI will listen to a specific port locally to receive callbacks, so the verification is always successful at one time. When verifying Qwen, CLIProxyAPI will directly obtain authorization information from Qwen's verification server, so there will be up to 60 attempts.