Reverse Proxy Guide

This guide explains how to convert existing account JSON into a format Cockpit recognizes, then import it as a Codex account. When you manage many accounts, Cockpit's API service can schedule them together and reduce how often you switch accounts by hand.

Prepare

Before you start, make sure you have:

• the account JSON file downloaded after redeeming on the platform, commonly in the CPA or sub2api format;
• Codex installed and launched at least once;
• a Cockpit installer that matches your operating system and processor architecture.

Cockpit's interface and features change across versions. The screenshots here show where each action lives. When a button name or layout differs from your version, follow the actual interface.

Step 1. Convert the JSON format

Different tools use slightly different JSON structures. Before importing into Cockpit, convert your existing file to the Cockpit format.

1. Open the ChatGPT Session Converter.
2. Choose Cockpit as the output format.
3. Click Choose file and import one or more JSON files.
4. Review the result, then click Download JSON.

Choose the Cockpit output format, import your source files in bulk, then download the converted result.

Converted files are still sensitive credentials

After converting, keep both the source and output files on a trusted device. When you are done, close any sharing, sync, or temporary upload channels to avoid leaking session credentials.

Step 2. Download and install Cockpit

1. Open Cockpit Tools Releases.
2. Pick the installer for your operating system and processor architecture. For example, 64-bit Windows usually uses the file whose name contains x64-setup.exe.
3. Prefer the current stable release; if a newer version has compatibility issues, roll back based on the release notes.
4. After installing, launch Cockpit and confirm you can reach the dashboard.

The Cockpit dashboard. The next steps start from the Codex entry on the left.

Step 3. Import your Codex account

1. Open account management

In the left navigation, select Codex to open the account overview, then click the plus button in the top-right corner.

Open the Codex account overview and click the plus button in the top-right to add an account.

2. Import from a local file

In the "Add Codex account" window:

1. Switch to Import.
2. Click Import from local file.
3. Select the JSON file converted in Step 1. You can select multiple files to import several accounts at once.

Choose "Import", then pick the converted JSON file from your local device.

3. Set the Codex path and launch

Once the import finishes, the account appears in the list. Before the first launch, open Cockpit settings and confirm the Codex launch path is correct; if you are unsure of the path, start with the automatic detection or default option the software provides.

To use a single account, click the Launch button at the bottom of its account card.

Every account card has its own launch button at the bottom.

Still prompted to sign in after launch

First check that the Codex launch path is correct and that the account JSON imported successfully. If a single-account launch keeps asking you to sign in, switch to the API service in the next section to manage accounts centrally.

Step 4. Configure the API service

When you have many accounts, closing Codex, switching accounts, and relaunching one by one interrupts your workflow. The API service lets you add several imported accounts to one service, and Cockpit schedules them based on availability.

1. Add service members

On the Codex account page, find the API Service card and click the Add member button at the bottom of the card.

Click the add member button at the bottom of the API service card.

2. Select accounts and save

1. Check the accounts you want to add to the service, or use select all.
2. To include Free accounts, leave Restrict Free accounts unchecked.
3. Click Save collection.

Select the service members; leave the restriction unchecked when you want to use Free accounts.

3. Start the API service

After saving, return to the account overview and click Start at the bottom of the API service card. Once the card shows "Running", launch or connect Codex through Cockpit.

The API service card may offer modes such as "Standard" and "Fast". Mode availability, actual speed, and account limits depend on your Cockpit version and account status, so follow the notes in your current interface.

Step 5. Avoid missing session history

Single-account mode and the API service use different launch and session-management flows. Once you settle on one approach, try not to switch back and forth often, or past sessions may become temporarily invisible.

If a session does not show up:

1. Open Session Management at the top of the Codex account page.
2. Check the sessions you want to restore; use select all for bulk work.
3. Click Repair visibility, then refresh the list when it finishes.

Select records in session management, then use "Repair visibility".

Do not clear the .codex directory directly

Restoring sessions may create duplicate local records under %USERPROFILE%\.codex. Back up the whole directory and quit Codex before deleting anything; do not remove files manually when you are unsure what they do, or you may lose chat history permanently.

Final checklist

Once configured, confirm each item:

• the JSON is converted to the Cockpit format and stored on a trusted device;
• Cockpit recognizes every Codex account you need to use;
• the Codex launch path is correct, and a single account or the API service starts normally;
• the API service members and Free account restriction match your actual needs;
• past sessions are visible, and the local .codex directory is backed up.

If your interface differs from the screenshots, check your Cockpit version and release notes first, then complete each action using the current button names.