Feature IDEA: poll twitter for upcoming limit resets and report them and use them in calculations

[christophsturm]

codexbar could poll @thsottiaux twitter account and then take upcoming limit resets into account, then i get a notification that i can spend as much of my remaining 20% in the next 5 hours because it will reset.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Latest ClawSweeper review: 2026-05-22 09:34 UTC / May 22, 2026, 5:34 AM ET.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Summary
Keep open: this is a real feature idea, not an already-implemented bug fix, and current main has no Twitter/X polling path for reset announcements. Using an unofficial social account in quota math would need maintainer product/privacy judgment before any implementation.

Reproducibility: not applicable. this is a feature request, not a reported failure. Source inspection shows current main has reset countdowns and pace calculations, but no Twitter/X reset-announcement integration to reproduce.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Include redacted logs or terminal output.

Next step
Manual review is appropriate because the remaining decision is whether CodexBar should depend on an unofficial Twitter/X source and how to make that opt-in/private, not a narrow fix.

Review details

Best possible solution:

If maintainers want this, add an opt-in, tested external reset-announcement source behind existing provider settings and keep official OAuth/CLI/dashboard reset windows authoritative by default.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a feature request, not a reported failure. Source inspection shows current main has reset countdowns and pace calculations, but no Twitter/X reset-announcement integration to reproduce.

Is this the best way to solve the issue?

No, not as stated: hard-coding social polling into quota math is not the narrowest maintainable path. The safer direction would be an explicit maintainer-approved, opt-in external reset source with tests, fallback behavior, and privacy expectations.

Label changes:

• add P3: This is a speculative feature idea with no broken current workflow and clear product-policy questions before implementation.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P3: This is a speculative feature idea with no broken current workflow and clear product-policy questions before implementation.

What I checked:

• Current Codex sources are official/local, not social polling: The Codex provider docs list OAuth, OpenAI web dashboard, CLI RPC, CLI PTY diagnostics, and local cost scans as data sources; reset windows come from dashboard text or CLI/RPC responses. (docs/codex.md:12, 123fe84ef026)
• Provider reset windows are first-class current behavior: The README describes per-provider reset countdowns, provider status polling, privacy-first local/session data handling, and optional session quota notifications, but not third-party announcement feeds. (README.md:20, 123fe84ef026)
• Quota math is built around RateWindow metadata: RateWindow stores used percent, window duration, and reset timestamp; Codex RPC/OAuth mapping fills those fields from provider responses. (Sources/CodexBarCore/UsageFetcher.swift:3, 123fe84ef026)
• Pace calculations already use reset timestamps and history: Weekly pace uses the current RateWindow plus optional Codex historical samples; non-Codex generic pace requires explicit window duration rather than an external announcement source. (Sources/CodexBar/UsageStore+HistoricalPace.swift:9, 123fe84ef026)
• Repository scope requires sign-off for this kind of feature: VISION.md says new features and changes adding meaningful maintenance complexity need sign-off; a Twitter/X poller would add both an external dependency and calculation policy. (VISION.md:13, 123fe84ef026)
• No existing Twitter/X reset integration found: A repository-wide search for thsottiaux, Twitter/X polling, and reset-announcement terms only found project/social links and existing reset-calculation code, not a provider implementation. (123fe84ef026)

Likely related people:

• steipete: Current blame for the Codex reset pace, usage pace text, and UsageFetcher reset mapping code is attributed to Peter Steinberger at the v0.28.0 release boundary. (role: current reset/pace area owner; confidence: medium; commits: 2db843a4600f; files: Sources/CodexBar/UsageStore+HistoricalPace.swift, Sources/CodexBar/UsagePaceText.swift, Sources/CodexBarCore/UsageFetcher.swift)
• zhulijin1991: The changelog credits recent Codex weekly pace reserve and historical reset-bucketing work to this handle, which is close to the requested calculation behavior. (role: adjacent contributor; confidence: medium; commits: 2db843a4600f; files: CHANGELOG.md, Sources/CodexBar/UsageStore+HistoricalPace.swift)
• m1qaweb: The changelog credits OpenAI dashboard reset-line parsing work to this handle, adjacent to the source that currently supplies Codex/OpenAI reset timestamps. (role: adjacent contributor; confidence: low; commits: 2db843a4600f; files: CHANGELOG.md, docs/codex.md)
• johnlarkin1: The changelog credits usage pace support for explicit reset windows to this handle, which overlaps the proposed calculation policy. (role: adjacent contributor; confidence: low; commits: 2db843a4600f; files: CHANGELOG.md, Sources/CodexBar/UsagePaceText.swift)
• ViperThanks: The changelog credits usage pace support for explicit reset windows to this handle, which overlaps the proposed calculation policy. (role: adjacent contributor; confidence: low; commits: 2db843a4600f; files: CHANGELOG.md, Sources/CodexBar/UsagePaceText.swift)

Remaining risk / open question:

• The requested source is an unofficial Twitter/X account, so authority, availability, rate limits, authentication, and parsing stability are unresolved.
• Using social posts in quota calculations could notify users to spend quota based on a non-authoritative signal unless maintainers define precedence and fallback behavior.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 123fe84ef026.