AI Quota Tool

Monitor your remaining AI quota for Claude, GitHub Copilot, OpenAI Codex, and Grok, plus the balance or spend of your DeepSeek, Kimi, OpenRouter, Anthropic, and OpenAI API keys - live in VS Code.

How sign-in works (Claude, ChatGPT / Codex, Grok, Gemini, Cursor):

• To sign in, this extension opens Chrome or Edge in a new, separate profile. You sign in on the real site. The extension never sees your password.
• After you sign in, it reads one session cookie from that profile, stores it in VS Code SecretStorage, and deletes the profile.
• It sends the cookie only to the same provider, to read your usage. There is no server of ours.
• It never reads your own browser profile.

Copilot uses the VS Code GitHub sign-in. API keys that you add go only to their own provider. Your use of each service follows that service's terms: Anthropic, OpenAI, xAI, Google, Cursor. Read the privacy policy and the source on GitHub.

Features

• Status bar item - remaining quota at a glance for each Account (the lower of session and weekly %). The tooltip lists each Key. The item turns amber when an Account or a Key with a real percent drops below 10%, or when a Key balance is zero.
• One panel, three tabs - Usage shows your Accounts and Keys. Accounts lets you sign in to each plan. Keys lets you add API keys.
• Lowest remaining - the Usage tab starts with the one limit that has the least left, and when it resets.
• Account cards - one card for each signed-in Account, with segmented session, weekly and monthly gauges. Copilot and Grok show an honest status when a percent is not available.
• Fits your theme - the panel uses the colors and fonts of your VS Code theme: dark, light and high contrast. In a wide tab the cards show as a grid.
• Grok - sign in on the Accounts tab.
• Gemini (high risk) - sign in on the Accounts tab to see the 5-hour and weekly windows. Google can bind its session cookies to the browser, so this session can end within hours.
• Cursor - sign in on the Accounts tab to see the monthly usage (the lowest pool). You see short-window rate limits, plus the SuperGrok weekly pool when available.
• Named Keys - add many API keys on the Keys tab, each with its own name. After you save a Key, the panel shows only its last 4 characters.
  • DeepSeek and Kimi show the account balance (money left, not a percent).
  • OpenRouter shows the spend of that one key. If the key has a limit, it shows the spend against the limit and the real percent left. If not, it shows the spend this month.
  • Anthropic and OpenAI (Admin key only) - show the org spend for the current month. An Admin key can manage your whole org, so the add form asks you to confirm it. The extension uses the key only to read the cost report.
  • Budget - on a Key that shows spend only, click Edit and set a monthly budget. The Key then shows the spend against the budget and the percent left. With no budget, it never shows a percent.
• Standalone - fetches quota directly from VS Code with your session credentials. No Chrome extension required.
• Optional Chrome push - if you also run the Chrome package, it can merge readings over a local WebSocket (freshest wins). Not required.
• Automatic refresh - each Account refreshes every 5 minutes, only while the VS Code window has focus. Each Key refreshes every 5 minutes. A new sign-in or a new Key refreshes at once.

Setup (one time)

1. Install the extension
2. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
3. Run "AI Quota Tool: Set Up Accounts". The panel opens on the Accounts tab.
4. Click Sign in for each service that you use. A new Chrome or Edge window opens. Sign in there, then click Done in VS Code. Each service is optional. To paste a cookie yourself, click Paste instead.
5. To add a DeepSeek or Kimi API key, open the Keys tab and click Add key.

How to get each credential

Claude session key (claude.ai usage bars - not an Anthropic Console API key). Sign in opens a browser window and reads the key for you. To paste it yourself, click Paste instead, or set aiQuotaTool.browserSignIn to false:

1. Open claude.ai in Chrome and sign in
2. Open DevTools (F12) → Application tab → Cookies → https://claude.ai
3. Copy the value of sessionKey (starts with sk-ant-sid)

GitHub Copilot - click Sign in with GitHub on the Accounts tab. VS Code shows one dialog to use your VS Code GitHub account. You do not copy a code or a token. The card shows the percent left and the reset time for each limited quota (premium requests, or chat and completions on the Free plan). A quota with no limit shows the AI credits used. If GitHub does not give these numbers, the card shows your seat status instead of inventing 100%.

ChatGPT session token (for Codex)

1. Open chatgpt.com in Chrome and sign in
2. Preferred: DevTools → Network → any chatgpt.com request → Request Headers → copy the full Cookie value and paste it in line 1 on the Accounts tab
3. Or: Application → Cookies → if you see __Secure-next-auth.session-token.0 and .1, that is one session split for size. Double-click each Value (full text, not …), paste .0 on line 1 and .1 on line 2
4. Test and save exchanges cookies for a short-lived access token, then reads usage

Important: Do not glue .0+.1 into a single un-named string. The browser sends them as two cookie names; the extension does the same.

Grok sso cookie (grok.com short-window remaining)

1. Open grok.com in Chrome and sign in
2. Open DevTools (F12) → Application tab → Cookies → https://grok.com
3. Copy the value of sso (JWT, often starts with eyJ)

DeepSeek API key (platform.deepseek.com account balance)

1. Open platform.deepseek.com and sign in
2. Go to API keys and create or copy a key
3. On the Keys tab, click Add key, choose the provider, and paste the key

Kimi API key (platform.kimi.ai account balance)

1. Open platform.kimi.ai and sign in
2. Go to API keys and create or copy a key
3. On the Keys tab, click Add key, choose the provider, and paste the key

Use Test and save to test a secret before the extension keeps it. Use Sign out on the Accounts tab, or Remove on the Keys tab, to delete a secret. Use Edit on the Keys tab to change the name of a Key. To change the value of a Key, remove it and add it again.

If you saved a DeepSeek or Kimi key in version 0.9, it becomes the Key "DeepSeek key 1" or "Kimi key 1". You do not need to add it again.

Usage

Click the status bar item ($(pulse) AI Quota) to open the Usage tab.

Optional: Chrome package (legacy)

A Chrome extension package may exist in this monorepo for optional browser-session push. It is not part of the VS Code V1 product bar. This extension works fully standalone.

Privacy and security

This extension stores the Claude sessionKey, the ChatGPT session token, the Grok sso cookie, and each API key that you add. Copilot uses the VS Code GitHub sign-in, and VS Code keeps that token. It keeps them in VS Code SecretStorage. Read the privacy policy.

• Session cookies and API keys are account-level secrets. Treat them like passwords.
• Stored only in VS Code SecretStorage on this machine (encrypted at rest by the host OS / VS Code), not in plain-text settings or our servers.
• Secrets are sent only to the owning service (claude.ai, chatgpt.com, grok.com, api.deepseek.com, api.moonshot.ai, openrouter.ai, api.anthropic.com, api.openai.com, or GitHub APIs) for quota reads - no telemetry backend.
• Lifecycle: Test and save tests the secret before the extension keeps it. Sign out or Remove deletes the secret.
• Invalid or expired sessions remove the old reading and show Session ended on the card and in the status bar. The secret is not auto-deleted. Open the Accounts tab to sign in again or sign out. Stale “full quota” is never invented.
• Optional local WebSocket (127.0.0.1) may receive quota updates from the Chrome extension; any process on your machine could spoof that channel.

Requirements

• VS Code 1.95 or later
• Active accounts on the services you want to monitor (Claude Pro/Free, GitHub Copilot, ChatGPT, Grok, DeepSeek, Kimi, OpenRouter)

Publishing (maintainers)

Releases go to the Visual Studio Marketplace under publisher BasantPandey via a manual GitHub Actions workflow. Every live publish increments the extension version and pushes a git tag.

One-time setup

The workflow signs in with Microsoft Entra ID through GitHub OIDC. There is no PAT and no stored secret. (Azure DevOps stops accepting global PATs on 2026-12-01.)

1. Create a managed identity. In the Azure portal, open Managed Identities → Create. Use any resource group and region. Use a user-assigned managed identity, not an app registration: an app registration signs in but the publish fails with InvalidAccessException.
2. Trust this repo. Open the identity → Settings → Federated credentials → Add credential:
   • Scenario: GitHub Actions deploying Azure resources
   • Organization: BasantPandey, Repository: AIQuotaTool
   • Entity type: Environment, name: marketplace-publish
3. Add two repository secrets (Settings → Secrets and variables → Actions): AZURE_CLIENT_ID and AZURE_TENANT_ID, from the identity's Properties page. They are ids, not passwords.
4. Create the environment marketplace-publish (Settings → Environments). Optional: add yourself as a required reviewer, so each live publish waits for your approval.
5. Add the identity to the publisher. Run Actions → Show Marketplace identity id → Run workflow one time. Copy the id from the run summary. Then open the publisher page → Members → Add, paste that id, and choose Contributor.
6. Keep Settings → Actions → General → Allow GitHub Actions to create and approve pull requests turned on. The workflow opens a release PR, because main is protected.

Run a release

1. Open Actions → Publish VS Code extension. Click the gray Run workflow button on the right. A form opens.
2. Fields in the form:
   • Branch (ref) - branch to ship (default main; use a branch name, not a raw SHA, for live runs)
   • Version bump (bump) - patch (default), minor, major, or none. Use none when a merged PR already set the version in package.json. Then the run tags and publishes that version, with no release PR.
   • Dry run (dry_run) - leave checked to package only (no bump, no Marketplace). Uncheck for a live release.
   • A dry run needs no Azure setup. A live run needs steps 1 to 5 above. If the environment has required reviewers, every run waits for your approval.
3. Prefer a dry run first; download the .vsix artifact and confirm it installs.
4. Live run: uncheck dry_run → workflow bumps package.json, commits to release/vscode-vX.Y.Z, tags vscode-vX.Y.Z, opens a release PR, packages, then runs vsce publish --azure-credential.
5. Merge the release PR after CI passes. This puts the new version on main.
6. Verify the listing: Marketplace manage (BasantPandey)

Local package (no publish)

pnpm install
pnpm turbo build
pnpm --filter ai-quota-tool-vscode run package

Spec

Pipeline product requirements: Spec: VS Code Marketplace publish pipeline

Screenshots

The images in docs/ come from the real dashboard build. Make them again after a design change:

pnpm turbo build
node scripts/vscode-assets.mjs

The script also makes the extension icon (icons/icon128.png) from the brand mark.