gitwtfhub

wtf is cpa-account-config-manager?

mxucc/cpa-account-config-manager — explained in plain English

Analysis updated 2026-05-18

14GoAudience · ops devopsSetup · moderate

TL;DR

A web-based management plugin for CLIProxyAPI that lets operators view, edit, and health-check many AI provider accounts at once.

Mindmap

mindmap
  root((cpa-account-config-manager))
    What it does
      Account list and search
      Health inspection
      Batch edits with preview
      Credential export
    Tech stack
      Go
      React
      CLIProxyAPI plugin ABI
    Use cases
      Manage many AI accounts
      Auto disable unhealthy accounts
      Bulk configuration changes
    Audience
      Operators
      DevOps teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Manage a large list of AI provider accounts behind CLIProxyAPI from one dashboard instead of editing config files.

REASON 2

Automatically detect and disable accounts hitting rate limits, then re-enable them once quota resets.

REASON 3

Preview and apply batch edits, like priority or proxy settings, across many accounts safely.

REASON 4

Export account credentials or usage reports in formats compatible with several related proxy tools.

What's in the stack?

GoReact

How it stacks up

mxucc/cpa-account-config-managergizmodata/adbc-driver-quackgokele/ovh
Stars141414
LanguageGoGoGo
Setup difficultymoderatemoderatemoderate
Complexity3/53/5
Audienceops devopsdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 1h+

Requires an existing CLIProxyAPI deployment supporting the native plugin ABI version 1 before this plugin can be installed.

Wtf does this do

This project is a plugin for CLIProxyAPI, a separate tool that lets people run one proxy in front of multiple AI provider accounts, such as accounts for Codex, Claude, Gemini, and xAI. Rather than editing raw configuration files by hand every time an account needs a change, this plugin adds a web interface for managing those accounts directly. Through the plugin, an operator can see a dense list of every configured account, with details like provider, account type, status, and usage counts, and can search or filter that list. It can create, edit, and delete accounts, and supports safe batch edits with a preview step before anything is written, so changes to many accounts at once can be reviewed first rather than applied blindly. One of its bigger features is account health inspection. It can check accounts on a schedule or manually, using the proxy's own request history and usage data, and flag accounts that look unhealthy, for example ones hitting rate limits repeatedly. Based on configurable rules, it can automatically disable accounts that fail checks and later re-enable them once their limits reset, and can optionally delete accounts that stay disabled for too long, though every automatic and destructive behavior defaults to off until an operator turns it on. Other features include exporting account credentials in formats used by several other related tools, generating usage reports in JSON and CSV, a persistent history log of every change made through the plugin, and support for importing accounts from pasted text or uploaded files. The interface is built with React and supports light, dark, and several language options. The plugin explicitly does not handle refreshing tokens or reauthorizing accounts with the AI providers themselves. It only manages configuration and status around accounts that are already set up. The full README is longer than what was shown.

Yoink these prompts

Prompt 1
Explain what CLIProxyAPI native plugins are and how this one integrates with them.
Prompt 2
Walk me through installing this plugin's release archive for my platform and architecture.
Prompt 3
Show me how the account health inspection and automatic disable rules work.
Prompt 4
Help me understand the preview-confirmed batch edit workflow before I overwrite account fields.
Prompt 5
Explain how to export selected accounts in sub2api or Codex-Manager credential format.

Frequently asked questions

wtf is cpa-account-config-manager?

A web-based management plugin for CLIProxyAPI that lets operators view, edit, and health-check many AI provider accounts at once.

What language is cpa-account-config-manager written in?

Mainly Go. The stack also includes Go, React.

How hard is cpa-account-config-manager to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is cpa-account-config-manager for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.