gpt-account-manager
Self-hosted operations workspace for mailbox intake, refresh queues, and deployable maintenance workflows.
A self-hosted Python web app for managing multiple OpenAI and ChatGPT accounts in bulk, it runs OAuth credential refreshes, diagnoses failures like expired tokens or account bans, and exports auth files compatible with proxy API services.
This project is a self-hosted web application for managing multiple OpenAI and ChatGPT accounts in bulk. It is written in Python and aimed at people who need to maintain a large collection of accounts that rely on either Microsoft Outlook mailboxes or temporary email addresses to receive verification codes. The README is written entirely in Chinese.
The tool has two main sides. Regular users connect their own email credentials, receive verification codes through the interface, and submit accounts needing credential refreshes into a processing queue. A site administrator handles maintenance tasks, extracts temporary email tokens, and manages a central store of account credentials used for API access.
When accounts need their credentials renewed, the tool runs an OAuth flow against OpenAI, diagnoses why a credential failed (options include expired refresh tokens, session expiry, account bans, regional restrictions, or quota exhaustion), and exports the result as an auth JSON file compatible with proxy API services. Each stage of this workflow has its own browser page: one for the main account management view, one for the refresh queue, one for the credential warehouse, one for local format conversion, and an admin-only section for site maintenance.
By default, user data including email addresses, passwords, refresh tokens, and cached messages stays in the browser's local storage rather than on the server, so multiple people can share one instance without seeing each other's data. When server-side features are needed, data is stored under a per-user workspace identifier.
Deployment requires running the Python server directly or placing it behind a reverse proxy such as Nginx. No frontend build step is needed because the interface is plain HTML. Node.js is also required for the OAuth refresh step. The project has 17 stars on GitHub and does not appear to offer a hosted version.
Where it fits
- Centrally manage a large pool of OpenAI accounts, refreshing credentials automatically and diagnosing failures like expired tokens or regional bans
- Export refreshed auth JSON files for use with proxy API services that need valid OpenAI credentials
- Share one self-hosted instance across a team without exposing each other's account data, since credentials stay in each user's browser local storage