This Chrome extension automates the complex process of registering and logging into OpenAI accounts via OAuth, specifically designed for users needing to manage bulk account creation or testing. It streamlines the entire workflow, from obtaining OAuth links from a CPA panel to verifying callbacks, significantly reducing manual effort and potential errors.

How It Works

The extension operates as a multi-step automation tool, orchestrated through a sidebar interface. It sequentially handles obtaining OAuth authorization links from a user-provided CPA management panel, navigating to OpenAI's registration or login pages, filling credentials, fetching verification codes via integrated email services (QQ, 163, Inbucket, or DuckDuckGo temporary emails), and confirming OAuth consent. A key feature is its use of the Chrome debugger to programmatically click the "Continue" button on the OAuth consent page and listen for the local callback URL, enabling near-complete automation of the process. Runtime states are managed in session storage, while configurations persist locally.

Quick Start & Requirements

• Installation: Load the unpacked extension in Chrome via chrome://extensions/ after enabling developer mode.
• Prerequisites: Chrome browser, enabled extension developer mode, a compatible CPA management panel, and a configured email service for verification codes (DuckDuckGo with QQ/163/Inbucket, or manual email).
• Configuration: Settings are managed via the extension's sidebar, including the CPA OAuth URL, email service preferences, mailbox details (for Inbucket), and password management.

Highlighted Details

• Multi-Round Automation: Supports running the entire registration/login flow multiple times automatically.
• Diverse Email Support: Integrates with QQ Mail, 163 Mail, and Inbucket for verification code retrieval, alongside DuckDuckGo Email Protection for generating temporary @duck.com addresses.
• Automated OAuth Consent Click: Utilizes Chrome debugger to automatically click the "Continue" button on the OAuth consent page and capture the local callback.
• Robust State Management: Differentiates between session-level runtime state (current step, credentials) and persistent local storage for user configurations.

Maintenance & Community

No specific details regarding maintainers, community channels (like Discord or Slack), or project roadmap were found in the provided documentation.

Licensing & Compatibility

The license type and any compatibility notes for commercial use or closed-source linking are not specified in the provided README.

Limitations & Caveats

The automated OAuth confirmation step (Step 8) is highly sensitive to changes in the target page's DOM structure. Automatic DuckDuckGo email acquisition and CPA panel interactions also depend on the exact DOM structure matching the script's selectors. The button name "Manual OAuth Confirm" for Step 8 is outdated, as the code now attempts an automatic click. The callback URL capture is strictly limited to specific localhost or 127.0.0.1 formats.