A
licenseNot graded
qualityC
maintenanceEnables users to schedule and manage prompts for Codex CLI sessions, supporting one-time, interval, and cron triggers for both existing and newly created sessions.
1
MIT
quota-aware-resumer
by cher9lie
Related Servers
Alternatives to quota-aware-resumer
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceCoordinates concurrent Codex tasks around a shared ChatGPT quota snapshot, deferring expensive work near exhaustion and storing resumable checkpoints.58MIT
- AlicenseNot gradedqualityAmaintenanceEnables reviewing and dispatching existing Codex tasks across projects through a lightweight control panel, including scanning task inventories, confirming Continue or Optimize prompts, and tracking dispatch progress.1MIT
- AlicenseBqualityBmaintenanceEnables governed Codex work sessions by planning bounded segments, maintaining capacity reserves, and creating checkpoint-based resume contracts so long-running jobs can pause and resume deterministically within quota limits.3MIT
- AlicenseAqualityAmaintenanceEnables a Chief of Staff client to find Codex tasks, create and submit project work with exact prompts, track progress via durable receipts, and continue or manage the same conversation locally.102MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to create, update, delete, list, and inspect OS-native scheduled tasks and their logs across Windows, Linux, and macOS through a unified interface.-
TDQS
B3.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool maps to a distinct action and resource: display control center, refresh snapshot, upsert policy, sync policy state, upsert prewarm, and sync prewarm state. The policy vs prewarm and upsert vs set distinctions are clear and unlikely to be confused.
Naming Consistency4/5
Five of six tools consistently use the quota_resumer_ prefix with a verb_noun shape. The exception is open_quota_resume_control_center, which drops the prefix and changes 'resumer' to 'resume', creating a minor but noticeable inconsistency.
Tool Count5/5
Six tools is a well-scoped size for this domain, covering control-center interaction, state refresh, policy management, and prewarm management without unnecessary redundancy. Each tool has a clear purpose and earns its place.
Completeness3/5
The set covers core lifecycle operations through upsert and state sync, and the snapshot/control center tools provide visibility. However, there is no explicit delete/remove operation for policies or prewarm settings, and no detailed list/get beyond the aggregate snapshot, leaving cleanup of stale entries as a notable gap.
Maintenance
ActivityMaintained
ResponsivenessNo issues