DevQuota
Add to Chrome
§ CHAPTER ILIVE PREVIEW

One local extension.All quota signals.

DevQuota is a local-first Chrome extension for viewing AI coding quotas, reset windows, alerts, and activity across Claude, ChatGPT, Codex, Cursor, and GitHub Copilot. Quick reads live in the popup; deeper setup, delivery, and diagnostics live in the full workspace.

  • [✓] popup + full workspace
  • [✓] alerts + activity log
  • [✓] delivery + diagnostics
  • [✓] local-first state
devquota action popup
LIVE

ACTION POPUP · LIVE SNAPSHOT

Quota + runtime summary

PROVIDERS

4

ALERTS

3

ACTIVITY

18 events

DELIVERY

4

Claude Web
82% used
resets in 2h 14m5h window · auth ok
Codex Web / ChatGPT
stable
weekly + short-windowsession-backed
Cursor Web
94% used
monthly cyclecapacity + billing
GitHub Copilot Web
healthy
chat + premium reqsplan headroom

Reads signals from

  • Claude Web
  • Codex Web / ChatGPT
  • Cursor Web
  • GitHub Copilot Web

§ 01 · THE SIGNAL

Fast in the popup.
Deeper in the dashboard.

Use the popup for the immediate read. Open the workspace for sources, alerts, activity, delivery, setup, guide, diagnostics, and the in-extension policy pages.

See capabilities ↓
~/devquota · livewatching
$ devquota surfaces --all
→ 4 monitors · 3 active alerts · 18 recent events
[claude] 82% used · 5h window · resets in 02:14:06
[codex] stable · weekly + short-window healthy · last sync 2m ago
[cursor] 94% used · monthly capacity · billing cycle active
[copilot] healthy · chat + premium requests · auth ok
! delivery browser notifications on · 2 webhooks healthy · dashboard feed live
$

§ 02 · A POSITION

Local-first by design.
Explicit about the network path.

DevQuota keeps its own working state on this device and does not run a publisher analytics pipeline or hosted control plane. The runtime still talks directly to enabled providers, and it can send browser notifications, console output, webhooks, or TRMNL payloads only when you configure them.

PUBLISHER BACKEND

none

PROVIDER REQUESTS

enabled only

OPTIONAL DELIVERY

user-set

STORAGE

this device

§ 03 · PROVIDERS

Multiple monitors now.
More on the way.

Track Claude, ChatGPT, Codex, Cursor, and GitHub Copilot quotas from one browser extension workspace. API-based tracking and additional quota sources are part of the next expansion of the same workspace.

01

Claude Web

Session-backed quota visibility, reset timing, and auth health for Claude's rolling windows.

  • · 5h windows
  • · weekly limits
  • · auth state
02

Codex Web / ChatGPT

Short-window and weekly quota visibility for ChatGPT and Codex web sessions.

  • · 5h + weekly
  • · plan-aware
  • · webRequest auth
03

Cursor Web

Plan usage, billing-cycle health, and authentication checks for Cursor Web.

  • · monthly capacity
  • · billing cycle
  • · auth state
04

GitHub Copilot

Chat and premium-request quota visibility alongside the rest of your stack.

  • · chat quota
  • · premium requests
  • · plan headroom

§ 04 · CAPABILITIES

Beyond quota bars.
The rest of the workspace.

01 · ALERTS

Thresholds, cooldowns, and delivery outcomes.

The alert feed tracks quota, reset, billing, and authentication issues. Review what fired, where it was delivered, and what is still cooling down.

Dashboard · Cursor remaining capacity breached

Browser notification · Claude reset warning sent

Webhook · Ops bridge received the latest snapshot

02 · RESET WINDOWS

Precise countdowns. Plan-aware.

CLAUDE · 5H

02:14:06

CURSOR · MONTHLY

12d 03h

CODEX · WEEKLY

3d 06h

03 · ACTIVITY

A history of what happened.

Source syncs, webhook tests, TRMNL pushes, and delivery outcomes all land in the activity log.

18RECENT+4 syncs today

04 · SETUP

Guided setup, not guesswork.

STARTER FLOW

4 steps

05 · DELIVERY

4 channels

browser
console
webhooks
TRMNL

Test destinations, inspect failures, and keep alert routing in the same workspace.

06 · WORKSPACE MAP

From quick checks to deep diagnostics.

popup→dashboard→alerts + activity→settings + deliverysetup, webhooks, TRMNL, diagnostics
§ CHAPTER II

RUNTIME POSTURE · CURRENT BUILD

Local-first, with
explicit boundaries.

This section maps the current repo: local storage, provider host permissions, source-specific collection paths, and the optional delivery channels a user enables.

§runtime.posture.json
VERIFIED · LOCAL
// runtime posture, flattened and auditable
{
  "name": "DevQuota",
  "runtime": "browser-extension",
  "backend": null,
  "account": null,
  "publisher_telemetry": false,
  "publisher_hosts": [],
  "provider_hosts": [
    "claude.ai",
    "chat.openai.com",
    "chatgpt.com",
    "cursor.com",
    "github.com"
  ],
  "optional_delivery": [
    "browser-notifications",
    "console",
    "webhook",
    "trmnl"
  ],
  "storage": {
    "location": "this device",
    "medium":   "partitioned chrome.storage.local",
    "secrets":  "stored separately, encrypted when available"
  },
  "capabilities": {
    "read_session_signals": true,
    "persist_activity":     true,
    "dispatch_alerts":      true,
    "rewrite_prompts":      false,
    "act_on_behalf":        false
  },
  "providers_observed": [
    "claude.ai",
    "chatgpt.com",
    "cursor.com",
    "github.com/copilot"
  ]
}
repo-based · auditable§ verify below

§ DATA LEDGER

What we see · what we never see

WE SEE

  • + quota, billing, and reset responses from enabled providers
  • + auth state, refresh state, and alert transitions
  • + activity history and delivery diagnostics
  • + optional webhook or TRMNL endpoints you configure

WE NEVER SEE

  • — prompt text · completions
  • — file contents · source code
  • — a DevQuota cloud copy of your usage history
  • — anything unrelated to quota, billing, alerts, or delivery
Runtime network boundaryno DevQuota-owned collection host
ALLOWLIST · CURRENT BUILD
HOSTROLEPATHWHEN
claude.aiprovidercollectorClaude enabled
chat.openai.com / chatgpt.comprovidercollectorCodex enabled
cursor.comprovidercollectorCursor enabled
github.comprovidercollectorCopilot enabled
user webhook URLoptionaldeliveryonly if configured
TRMNL plugin URLoptionaldeliveryonly if configured

§ VERIFY

— three checks to confirm the current runtime shape

CHECK · 01devtools

Open DevTools and confirm requests go only to enabled providers or user-configured delivery endpoints.

// expected:
no DevQuota-owned host
provider and webhook traffic only when enabled
CHECK · 02manifest

Inspect the extension manifest. host_permissions list only the provider surfaces the collectors need.

host_permissions: [
  "chat.openai.com/*",
  "chatgpt.com/*",
  "claude.ai/*",
  "cursor.com/*",
  "github.com/*"
]
CHECK · 03storage

Run in the extension's service worker console:

> chrome.storage.local.get()
> // entire dataset, local

§ POSITION

Most monitoring products route state into a hosted control plane. DevQuota does not. It stores its own working set locally, talks directly to enabled providers, and only sends deliveries to endpoints the user explicitly configures.

Full privacy noteTerms & license

§ CHAPTER III · HOW

Three moves. One workspace.

  1. 1

    INSTALL

    Add the extension.

    Install the Chrome extension and open the integrated workspace in a full tab.

  2. 2

    RUN SETUP

    Turn on the monitors you use.

    Use Setup or Sources to enable providers, pick defaults, and decide how alerts should surface.

  3. 3

    WORK THE SURFACES

    Use the popup for speed and the dashboard for everything else.

    Quota cards, alerts, activity, delivery channels, setup, guide, and developer diagnostics all live inside the extension.

    Install it

§ CHAPTER IV · FAQ

Answers,
compressed.

Still have questions? Use the contact page for support, bugs, and policy questions.

Q.01Is DevQuota a SaaS dashboard or a browser extension?

DevQuota is a local-first Chrome extension with its own popup and full dashboard workspace. There is no hosted control plane, no web account, and no publisher-managed cloud workspace.

Q.02How do I track Claude, ChatGPT, Codex, Cursor, or GitHub Copilot quotas?

Install the extension, stay signed in to the providers you use in the same browser, and DevQuota reads quota, reset, and auth signals from those signed-in sessions with source-specific collectors where needed.

Q.03Can DevQuota show reset times, alerts, and activity in one place?

Yes. The current build includes the action popup plus Dashboard, Alerts, Activity, Setup, Guide, and a Settings workspace covering Sources, Alerts, Activity, Preferences, Delivery, Development, and About.

Q.04Does DevQuota send my quota history anywhere?

There is no DevQuota backend receiving your usage history. The extension stores state locally, talks to the providers you enable, and can send optional deliveries only to browser notifications, console, webhooks, or TRMNL endpoints you configure.

Q.05What can I configure?

Sources, thresholds, reset warnings, refresh cadence, browser notifications, console output, webhook destinations, TRMNL devices, activity retention, settings import and export, and developer log policy are all configurable inside the current workspace.

Q.06Which AI tools and browsers does DevQuota support today?

Today the build targets Chrome Manifest V3 and supports Claude Web, Codex Web / ChatGPT, Cursor Web, and GitHub Copilot Web. More monitors and API-based tracking are planned next.