Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add configurable low-quota threshold actions (pause / desktop alert)

Open
  • Is something wrong?
#5,649 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start by reading the existing quota threshold and proactive-switching behavior, then trace how quota observations, manual account pause, and quota-reset notification sinks work together. The issue names no files or tests, so locate those entry points before estimating the change. Done means selected quota windows can trigger the configured action, notifications include the requested quota details, and protected accounts are not routed new requests until manually resumed.

Written by the indexing model from the issue text.

Description

account-pool enhancement priority: P3

Area

Authentication and account pool / Dashboard / Platform notifications

What are you trying to accomplish?

I want OpenCodex to protect a Codex account before it is completely exhausted.

For example, if either the 5-hour or weekly quota reaches 80% used (20% remaining), I want OpenCodex to be able to automatically pause that account and/or alert me, instead of continuing to use it until the quota reaches 100%.

This is useful when I deliberately want to preserve the final part of my quota for later.

What prevents this today?

OpenCodex already has a configurable Usage threshold for proactive account switching, but that threshold is not a hard quota cutoff.

At the moment:

  • the threshold can change the warning state in the quota UI;
  • proactive switching can prefer a lower-usage eligible pool account;
  • Pause exhausted applies when an account is effectively exhausted;
  • there does not appear to be a setting that pauses an account when a configurable quota threshold is crossed;
  • there does not appear to be a desktop/system notification specifically for crossing that threshold.

This is especially noticeable with only one account in the pool: crossing the proactive-switch threshold does not protect the remaining quota because there is nowhere else to switch.

What should OpenCodex do?

Please add a configurable action for crossing a quota threshold.

Example behavior:

Low quota threshold: 80% used

Actions:

  • Warn only
  • Desktop/system notification
  • Pause account
  • Pause account + notification

The action should trigger when any selected quota window reaches or exceeds the configured used percentage. At minimum this should support the 5-hour and weekly Codex windows.

For automatic pause, the account should stop being eligible for new requests once the threshold is crossed, just as if I manually pressed Pause. Ideally it should remain paused until I manually resume it, so OpenCodex does not unexpectedly consume the reserved quota.

A notification should identify:

  • which account crossed the threshold;
  • which quota window crossed it;
  • current usage percentage;
  • reset time if known.

It would also be useful if this threshold/action were independent of the existing proactive-switch threshold, since switching and reserving quota are different policies.

Example usage or interface

In Codex Set → Advanced settings, something like:

Low quota protection
[✓] Enable

Threshold: 80% used

When threshold is reached:
[✓] Pause account
[✓] Show desktop notification

Apply to:
[✓] 5-hour quota
[✓] Weekly quota

Example result:

Main Account paused — Weekly quota reached 81% used (19% remaining). Resets Sep 27 at 10:32.

If another eligible account exists, normal routing can continue through that account. If none exists, requests should not silently continue through the protected/paused account.

Alternatives or workarounds

The current workaround is to watch the quota bars manually and press Pause before usage reaches the desired reserve level.

The existing proactive-switch threshold helps when another eligible account exists, but it does not provide a hard stop for a single account and is not the same as reserving quota.

Additional context

Tested against OpenCodex v2.63.0.

Relevant existing pieces already appear to exist in the codebase:

  • quota threshold / proactive switching;
  • manual account pause;
  • quota observation;
  • quota reset notification sinks (webhook / local command).

This request is specifically for a quota-crossing threshold action, not quota-reset notification.

Checks

  • I searched existing issues and documentation.
  • This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
  • I removed secrets and personal data.
Dominant language
TypeScript
Stars
16.9k
Forks
1.3k
Avg merge
7h 34m
Merged PRs (30d)
667

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lidge-jun/opencodex

All issues in lidge-jun/opencodex

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.