Developer tools1 sources·Published

Account-pool scheduler for Claude/Codex CLI with token-based billing

A developer built Clidex after repeatedly hitting rate limits and juggling multiple accounts with Claude/Codex CLIs: a scheduling layer with an account pool that keeps the native CLI workflow, bills per token instead of monthly, and mitigates 429 interruptions. An 'Earn' side lets users with idle Claude/ChatGPT quota host it for income — a two-sided market around wasted subscription capacity.

Score 701 sourcesConfidence 64%

The problem

Heavy Claude Code / Codex CLI users hit rate limits mid-task and manually switch accounts; subscriptions are flat-rate while usage is spiky, leaving paid quota idle. No tool keeps the native CLI experience while pooling accounts, scheduling around limits, and metering per token.

What could be built

A CLI-adjacent proxy: account pool with automatic failover on 429, per-token billing, native Claude/Codex CLI compatibility, plus a marketplace where users with idle quota earn from it. Distribution via the CLI communities already complaining about limits.

Who it's for

Claude Code / Codex CLI heavy usersusers with idle AI subscription quotasmall teams sharing AI accounts

Who is talking1

Related topics

Claude Codeaccount poolrate limittoken billing

Summaries are AI-generated. The original words are in the threads above.

Account-pool scheduler for Claude/Codex CLI with token-based billing · Magellan