Open source Codex + Claude Code · Local-first ↗

Protect AI agent quota.Project by project.

QuotaFence is an open-source quota manager for AI coding agents. It tracks Codex and Claude Code allowances, assigns weekly budgets to local folders, and helps prevent lower-priority work from consuming quota intended for critical projects.

Local-firstMulti-providerApache 2.0
QuotaFence
2 allowance windowsSynced just now
5-hour allowanceResets today at 19:29
62% left
Weekly allowanceResets in 4 days
74% left
Daily usageLast 6 months · 48 active days
6 months agoLessMoreToday
Model usageObserved token share
gpt-5.6-sol84%
gpt-5.513%
codex-auto-review2%
gpt-5.6-terra<1%

Allocations

Weekly quota · priority 1 is protected first

20% used65% planned35% free
ProjectWeeklyUsedLeftStatus
1project-a
40%15%
25%
Tracking
2project-b
25%5%
20%
Tracking
~/Code/project-a - qfence top
 QUOTAFENCE TOP   live local control plane

PROVIDER      5-HOUR            WEEKLY
Claude Code   ━━━━━━──  62%     ━━━━━━━━  74%
Codex         ━━━━━━━━  93%     ━━━━━━━─  85%

#  PROJECT      WEEKLY  USED  LEFT  STATUS
1  project-a    40%     15%   25%   ● allow
2  project-b    25%      5%   20%   ● allow

refreshed just now · live interval 30s

Shared limits create project-level blind spots.

Provider usage pages show account-level capacity. They do not give each local project an explicit weekly budget or priority when several agents share the same allowance.

See the limit. Decide where it goes.

QuotaFence combines provider allowance tracking, weekly folder budgets, local policy checks, and basic history without requiring a hosted account.

How it works
01
5-hour93%
Weekly85%

Track both allowance windows

See Codex and Claude Code 5-hour and weekly limits, reset times, sync health, and basic local usage history in one view.

02
project-a40%
project-b30%

Budget quota by project

Create, resize, remove, and reprioritize weekly project budgets from the desktop app or the interactive terminal UI.

03
qfence codex
Allowed2% reserved

Protect new work

Apply local Warn and Stop policies before a managed launch or a new prompt observed by a verified provider hook.

Awareness isn't control.

Without QuotaFence

  • One shared allowance with no explicit project budgets
  • No priority order when several projects compete for capacity
  • No local policy check before supported new work begins
  • Checking usage means leaving the terminal for a browser tab

With QuotaFence

  • Weekly budgets attached to real project folders
  • Priority determines which budget is protected first
  • Warn or Stop decisions based on current local policy
  • One local ledger for the CLI and desktop - no round-trip required

The same ledger, without leaving the terminal.

The same local ledger powers the desktop app and qfence. Monitor quota live, manage project budgets, and launch protected agents without changing context.

~/Code/project-a
❯ qfence top --once
 QUOTAFENCE TOP   live local control plane  interactive mode: qfence top

╭─────────────┬──────────────────────────────┬──────────────────────────────┬──────────────╮
│ PROVIDER    │ 5-HOUR                       │ WEEKLY                       │ SYNCED       │
├─────────────┼──────────────────────────────┼──────────────────────────────┼──────────────┤
│ Claude Code │ ━━━━━━──  70% ↻ today 12:00  │ ━━━━━━━━  90% ↻ tomorrow     │ ● 55s ago    │
│ Codex       │ ━━━━━━━━  93% ↻ today 16:22  │ ━━━━━━━─  85% ↻ Sep 15 04:21 │ ● 7s ago     │
╰─────────────┴──────────────────────────────┴──────────────────────────────┴──────────────╯

  PROJECT ALLOCATIONS
╭─────┬─────────────┬─────────────────────┬──────────┬──────────┬──────────┬──────────────╮
│ #   │ PROVIDER    │ PROJECT             │ WEEKLY   │ USED     │ LEFT     │ STATUS       │
├─────┼─────────────┼─────────────────────┼──────────┼──────────┼──────────┼──────────────┤
│ 1   │ Claude Code │ project-c           │ 15%      │ 2%       │ 13%      │ ● allow      │
│ 1   │ Codex       │ project-a           │ 50%      │ 12%      │ 38%      │ ● allow      │
│ 2   │ Codex       │ project-b           │ 30%      │ 6%       │ 24%      │ ● allow      │
╰─────┴─────────────┴─────────────────────┴──────────┴──────────┴──────────┴──────────────╯

  ●  Claude Code · 20% used over 30 days
  ··········▂···▄··············█
  10 Aug                  08 Sep

  ●  Codex · 35% used over 30 days
  ·▂▂█····▁·▂···▁···▁▁······▂·▁▂
  10 Aug                  08 Sep

  refreshed just now · live interval 30s
❯ qfence allocations add --provider codex --percent 20
PROJECT             WEEKLY   USED   LEFT   STATUS
project-a           50%      12%    38%    ● allow
project-b           30%       6%    24%    ● allow
project-c           20%       0%    20%    ● allow

# Resize, fund from another project, or change priority
❯ qfence allocations set project-c --percent 30 --from project-a
❯ qfence allocations move project-c up
❯ qfence codex
QuotaFence: launching Codex for project-a with 2 percentage points reserved (Weekly)

# Claude uses the same admission and reconciliation flow
❯ qfence claude

# Preview a decision without launching
❯ qfence admit codex
01

Connect

Sync the allowance windows returned by Codex or Claude Code.

02

Allocate

Give each local project folder a weekly budget and priority.

03

Protect

Check the active policy before supported new work begins.

04

Review

Reconcile provider movement and keep uncertain usage unattributed.

Desktop app, CLI, one local ledger.

Checking the latest release…

⌘Checking release

macOS

Universal DMG for Apple Silicon and Intel. Signing status is listed with each release.

View releases ↗
⊞Checking release

Windows

Unsigned x64 installer preview. Verify the published checksum before bypassing SmartScreen.

View releases ↗

Desktop downloads come from GitHub Releases. CI artifacts are temporary build outputs and are not used by these buttons. Read the installation guide →

What QuotaFence does, and what it does not.

What is QuotaFence?

QuotaFence is an open-source, local-first coding agent quota manager for Codex and Claude Code. It tracks provider allowance windows and lets you assign weekly budgets and priorities to local project folders.

Does QuotaFence read my prompts or source code?

No. QuotaFence does not intentionally collect or upload prompts, responses, source files, transcripts, provider credentials, or its local SQLite database.

Can it show exact token usage for every project?

No. Providers expose aggregate subscription usage, not exact subscription-token totals by folder. QuotaFence attributes supported managed activity and leaves ambiguous or concurrent activity explicitly unattributed.

Does it support both Codex and Claude Code?

Yes. Both providers support 5-hour and weekly allowance sync, weekly project budgets, managed CLI launches, and provider-specific desktop prompt integrations where available.

Is QuotaFence free?

The current core is open source under Apache 2.0 and includes project allocations, local enforcement, basic history, and desktop and terminal dashboards without a project-count limit.

We would rather say “we don't know” than guess.

01

Your policy stays on your device. Workspace metadata, allocations, and the managed-session ledger use local storage. No hosted account is required.

02

Capability claims match reality. QuotaFence distinguishes process control, trusted prompt admission, and observation-only tracking instead of treating them as equivalent.

03

Uncertainty remains visible. Concurrent or unmapped activity stays unattributed instead of being assigned to the wrong project.

Give important projects
room to finish.

Track Codex and Claude Code in one local dashboard, then turn shared weekly allowance into explicit project budgets and priorities.