Skip to main content

aiq — AI Quota

Monitor usage and switch between AI coding subscription accounts.

$ aiq
  AI Quota
  ────────────────────────────────────────────────────────────────────────
    TOOL     ACCOUNT                          5h            7d          STATUS
  ● claude   alice@example.com       ██████░░░░  62.3%  ████░░░░░░  38.1%  OK
    claude   bob@example.com                  —              —        --
  ────────────────────────────────────────────────────────────────────────
  ● codex    alice@example.com       ████████░░  81.0%  ██████████ 100.0%  LIMITED
    codex    bob@example.com         ██░░░░░░░░  15.2%  ███░░░░░░░  28.4%  OK
  ────────────────────────────────────────────────────────────────────────
  4 accounts · 2 ok · 1 limited · 1 unknown

What it does

  • Check quotas across Claude Max, Codex (ChatGPT Pro), and Gemini Ultra accounts
  • Switch accounts when you hit rate limits — auto-picks the one with most headroom
  • Vault management — save, list, and remove credential profiles locally

Install

uv tool install aiq-monitor

Or from source:

git clone https://github.com/elyase/aiq.git
cd aiq
uv tool install .

Usage

aiq                        # show quota for all accounts
aiq use codex              # auto-pick best Codex account
aiq use claude alice@x     # switch to specific account
aiq add codex alice@x      # save current auth as profile
aiq logout codex           # remove auth files
aiq ls                     # list all vault profiles
aiq rm codex alice@x       # remove a vault profile
aiq import                 # import from caam vault / active creds
aiq --json                 # machine-readable output

How credentials work

aiq never stores passwords or API keys. It copies the OAuth/session files that each tool's CLI already writes to disk (e.g., ~/.codex/auth.json) into a local vault at ~/.local/share/aiq/vault/. All vault files are stored with 0600 permissions.

Supported tools and their auth sources:

Tool Auth files read
Claude ~/.claude.json, macOS Keychain (Claude Code-credentials)
Codex ~/.codex/auth.json
Gemini ~/.gemini/settings.json, ~/.gemini/oauth_credentials.json

Agent setup

Give your AI coding agent the ability to monitor quotas and switch accounts automatically.

1. Install the CLI

uv tool install aiq-monitor

2. Install the skill

Using skills:

npx skills add elyase/aiq

This installs the aiq skill into your agent's skills directory. The agent will automatically use aiq when you hit rate limits or ask about quota.

3. Import your accounts

aiq import    # detects active logins for Claude, Codex, Gemini

Or add accounts manually:

# Log in to first account
claude           # /login with alice@example.com
aiq add claude alice@example.com

# Log in to second account
aiq logout claude
claude           # /login with bob@example.com
aiq add claude bob@example.com

# Switch back
aiq use claude alice@example.com

Now your agent can run aiq use claude to auto-switch when hitting limits.

Requirements

  • Python 3.12+
  • macOS (Keychain access for Claude; other tools work cross-platform)
  • humancli framework

License

MIT

Metadata

Release files for aiq-monitor 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aiq-monitor 0.1.0
File Size Uploaded
aiq_monitor-0.1.0.tar.gz 14.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aiq-monitor 0.1.0
File Interpreter ABI Platform
aiq_monitor-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 28.3 kB

Release files / aiq_monitor-0.1.0.tar.gz

Download URL aiq_monitor-0.1.0.tar.gz
Size 14.3 kB
Tags Source
SHA-256 checksum
How to use checksums
7e0812d846c1e0e1e5a788bab924a378d5f6441fb04aa672b33212e991e5d848
BLAKE2b-256 checksum
How to use checksums
0e9c97d4d6b930fae629303f298aeb68f6f5e2d89f9f7f26624eb87e826c9305
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 5, 2026.

Transparency log

Release files / aiq_monitor-0.1.0-py3-none-any.whl

Download URL aiq_monitor-0.1.0-py3-none-any.whl
Size 14.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
034526ec65c4c99800a0b0f315e64006b98f3dd30fcc1d57b711af7f9ade837f
BLAKE2b-256 checksum
How to use checksums
7ec3f6868376cf2fcb0792cb886244e95500b39e90ddc697097e8d320373ce6b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page