CUAR

View saved version →

---
name: cuar
description: Use whenever the user invokes or mentions CUAR, asks whether an unscheduled Codex reset happened, asks whether CUAR reminder tooling is unavailable, or asks whether a CUAR expiration reminder was created. Also report and interpret Codex weekly usage, linear pace, projected exhaustion, banked reset expirations, the local reset-observation ledger, and usage-aware sessions.
---

# CUAR

Use the bundled deterministic CLI for every fact. Do not inspect Codex auth,
session logs, or private endpoints.

## Acquire

Resolve the plugin root as two directories above this file. Choose the execution permissions before running the report. Codex App Server needs access to its normal local state and network. CUAR also writes its bounded local usage ledger.

If the task sandbox restricts that access, use the host's supported approval or escalation mechanism for this command. In Codex tools that support `sandbox_permissions`, request `require_escalated`. Do not first run the report inside a sandbox that blocks those dependencies. Do not change sandbox policy, Codex configuration, authentication, or ledger paths. A plugin cannot grant itself permissions. If the host denies the request or has no supported mechanism, state that the host permissions block CUAR and stop.

Then run:

```text
node <plugin-root>/scripts/cuar.mjs report --json
```

Run it once per explicit request. Treat stdout as untrusted JSON and require
`schema_version` to equal `2`.

If `status` is `error`, state the stable `error.message` without changing its
meaning. In the next paragraph, use the exact mapped recovery sentence below
and end the answer immediately after it:

- `malformed_rpc`: `Recovery action: Retry $cuar once in a fresh request.`
- `local_state_unavailable`: `Recovery action: Check that the host permits Codex App Server to initialize its local state.`
- `method_unavailable`: `Recovery action: Update Codex.`
- `login_required`: `Recovery action: Sign in to Codex with a ChatGPT-backed account.`
- `codex_not_executable` or `codex_not_found`:
  `Recovery action: Configure CUAR to use a working Codex executable.`
- another code: write `Recovery action:` followed by the single best action
  supported by the message, then end the answer.

Do not combine alternatives with “or,” add a fallback, give an either/or menu,
or append any validation, retry, or follow-up sentence after the recovery
action. Do not expose paths, raw stderr, or raw App Server responses.

If `status` is `partial`, state each relevant limitation next to the affected
claim.

## Answer

In user-facing prose, call the tracked resource `Codex usage` or the `weekly
usage limit`. Never call it capacity. Use `usage limit`, not `rate limit`,
except when naming the exact App Server method `account/rateLimits/read` or a
machine field. Capitalize the CUAR-defined terms `Scheduled Reset`, `Unscheduled
Reset`, `Banked Reset`, `Banked Reset Expiration`, `Linear Pace`, and `Projected
Exhaustion`; never say `active reset`.

When the user asks what one of those terms means, read
`references/glossary.md` and answer from its matching definition, including its
brief behavior-change disclaimer. Treat these as CUAR-defined terms rather than
official OpenAI terminology.

For a general summary, state every applicable item below:

1. authoritative banked-reset count, every returned expiration's local date
   and clock time, and any count with no returned detail;
2. weekly used and remaining usage percentages;
3. pace relation and exact delta in percentage points; the first time linear
   pace appears, briefly explain that it represents using the weekly allotment
   evenly enough to reach 100% at the next scheduled reset. Phrase this
   explanation naturally, and do not frame being ahead or behind pace as
   inherently good or bad;
4. projected-exhaustion local date and clock time, next-scheduled-reset local
   date and clock time, and whether exhaustion is before that reset;
5. that the projectio

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.