Codex Usage
QuotaLintExperimental · Updated September 21, 2026

Will this task fit before your quota runs out?

QuotaLint checks the task you are about to start against the Codex quota you actually have left, then calls it: start now, plan first, split the work, or wait for reset.

QuotaLint is included in the free Codex Usage menu bar app. There is no separate QuotaLint download.

macOS 13+ · Apple Silicon · Python 3 and the Codex CLI required

QuotaLint
Task
Migrate authentication and update affected tests
Current quota · read automatically
5-hour
18%
Weekly
62%
QuotaLint call
SPLIT FIRST
Fit probability 34%Task size Large

Illustrative rendering of the QuotaLint window in the Codex Usage Mac app.

The missing decision

Quota tells you how much is left. It does not tell you whether to start.

Knowing you have 22% left does not answer the question actually in front of you. Is this a typo fix, a safe medium implementation, or a multi-step migration that dies halfway through and leaves the branch in pieces? The meter reports the fuel. It says nothing about the distance.

One call, before you spend anything

Every check resolves to exactly one of four outcomes, with a fit probability and the judged size of the task.

START NOW

Enough apparent headroom to finish and validate a coherent unit of work.

PLAN FIRST

Likely workable, but resolve the important uncertainty before spending quota.

SPLIT FIRST

Cut the job down to one independently finishable unit.

WAIT FOR RESET

Current quota creates too much risk of dying halfway through.

On Mac

No quota entry. QuotaLint already knows.

Codex Usage is already reading your quota every 60 seconds. Open QuotaLint from the menu bar and that live state is handed to the check for you. You describe the task. That is the whole workflow.

Get QuotaLint for Mac
Filled in for you
  • 5-hour remaining %
  • Time until the 5-hour reset
  • Weekly remaining %
  • Time until the weekly reset
  • Pressure state
  • Observed session pace, when available

You supply: the task description.

How it works

  1. 1
    Describe the task

    One or two sentences about the job you are about to hand your coding agent. Not code, not a transcript.

  2. 2
    QuotaLint weighs scope against quota

    It judges the likely execution scope of the task, then reads that against the quota you actually have left right now.

  3. 3
    Get one call before you start

    A single decision, plus fit probability and the judged task size. Then you act on it.

The judgment runs on the TypeSafe System One model behind an endpoint on this site. QuotaLint is an experimental task-fit assessment — not an exact quota-cost predictor, not an OpenAI feature or endorsed product, not a prompt writer, and not an agent.

What actually leaves your machine

Normal Codex Usage quota monitoring stays on your machine. QuotaLint is the one part that does not: it makes a request only after you open QuotaLint, enter a task, and press Check task. Nothing is sent before that.

Sent for a check
  • The task description you typed
  • Coarse quota state
Never sent
  • Repository contents
  • File paths
  • Codex conversation history
  • Credentials
  • Diagnostics
  • Account identifiers

The task text lives in that window only and is never written to disk. Full detail in what this site sends and stores.

No Mac app? Run a manual check in your browser.

The web checker runs the same judgment, but a browser cannot read your local Codex state, so you supply the quota numbers yourself — from /status in the Codex CLI.

Open web checker

Know before you start.

QuotaLint ships inside the free Codex Usage menu bar app, where your current quota is already on screen.