Tibo Reset Early Warning

Tibo Reset Early Warning

Provide an early warning for upcoming Codex quota resets and explicit completion announcements without waking a model for every routine poll.

Operating model

1. Run scripts/check_feed.py locally on a schedule. It uses Python's standard library, a public feed, and local state; routine runs do not call a model.
2. Treat exit code 0 with no output as normal silence. Treat JSON Lines on stdout as new candidates; only then assess the text semantically.
3. Notify with red for explicit future timing, rollout, or an explicit reset announcement. Use yellow only for a credible tease without timing or completion. Completion takes priority over upstream tease labels.
4. Ignore jokes, negations, unrelated resets, API rate limits, questions, historical recaps, and unrelated API resets.
5. For completion announcements (e.g. “All reset for everyone”), say “已宣布重置”, not “提前预警” or a predicted countdown. Ask the user to verify their account; the post does not prove their balance has refreshed.
6. State the original post time, link, confidence, and inferred Beijing-time window. Clearly label inference.
7. Recommend starting valuable queued work only. Never recommend empty token burning.

If the feed is stale, unavailable, malformed, or not scoped to @thsottiaux, send no quota alert. Surface the operational error in logs.

Commands

python3 scripts/check_feed.py --state /tmp/tibo-reset-state.json --dry-run
python3 scripts/check_feed.py --state "$TIBO_RESET_WARNING_STATE"

The first normal run establishes a baseline and emits no historical alerts. Use --replay only for testing.

For scheduling and notification wiring, read references/scheduling.md. For publishing with GitHub Desktop, read references/github-desktop.md.