DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to watch pool quota, cooldowns, and plans in real time with Underclass

Open a live terminal monitor that shows in-flight requests, account states, and quota windows.

Who it is forA developer or operator running Underclass for a team of personal subscriptions who needs to know which accounts are cooling and when they return.

The problemWhen accounts cool down silently, it is unclear why requests are slowing or failing and when capacity comes back.

The outcomeA read-only dashboard shows which accounts are healthy, which are cooling and until when, and which plan each account uses.

What you need first

  • Rust toolchain with cargo, to run `cargo run -- serve` from the repo
  • openssl available on the machine, to generate the proxy key and UI token
  • At least one ChatGPT/Codex, GitHub Copilot, or Claude Code subscription you are entitled to use
  • opencode installed if you want to use the OpenAI-compatible path from that client
  • Read each provider's terms before pooling accounts; the README does not address this

Steps

  1. Run cargo run -- serve in one terminal and keep it running.
  2. In a second terminal, run underclass top (or utop from the Nix package).
  3. Read the PLAN column and the account status column, and note the cooldown deadlines shown for any cooling account.
  4. Press j or k to scroll the account list, and press q to quit when finished.

Prompt for your agent

In the underclass repo at <repo path>, with the server running, start `underclass top` and capture the account table. Expected output: one row per configured account with a status label and plan. Verify that each cooling account shows a reset time and that the PLAN column is filled or marked unknown.

Caveat. The README says top reads the monitor snapshot, which includes account labels and usage, so keep that terminal session away from shared screens.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page