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

feat(providers): mostrar vigencia declarada y saldo de resets de Codex

Open
  • Is something wrong?
#132 0 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
42/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust, typescript
Domain
desktop, full-stack

Research direction

Start with backend commit f01ff4a to understand the optional provider-metadata contract and attribution rules, then inspect frontend commit 3fcd10d for cards and usage circles. Run the Rust tests and the focused frontend tests, typecheck, suite, and build before validating the desktop representation. Done means provider-declared validity dates and Codex reset balances are shown when valid, while unknown, invalid, unattributed, failed, or stale data is omitted and gauges remain accessible.

Written by the indexing model from the issue text.

Description

status:approved type:feature
Pre-flight checks
  • I searched existing issues and found no duplicate.
  • I understand that this proposal requires product review before implementation.
Problem to solve

En main d097bc3, los informes no exponen fechas explícitas de vigencia ni el saldo de resets comunicado por Codex. Se propone recuperarlos sin inferir cancelaciones a partir de cuotas o caducidad OAuth.

Proposed solution

Añadir metadata opcional al contrato Rust/TypeScript y mostrarla en tarjetas y círculos, manteniendo autoridad del proveedor y atribución correcta de cuenta. Entregar en cadena: backend feat/recover-provider-metadata, después frontend feat/recover-usage-badges.

Affected area

Application behavior

Scope and non-goals
  • Exponer solo fechas comunicadas explícitamente por Codex, Cursor u OpenRouter; fin de periodo no equivale a baja.
  • Mostrar saldo de resets de Codex, conservando cero y sin convertir cuotas en créditos estimados.
  • Omitir metadata desconocida, inválida o no atribuible y no mostrarla como vigente en reportes fallidos/stale.
  • No enviar tokens ni claims completos al frontend ni usar metadata como autoridad de autenticación.
  • Conservar accesibilidad, identidad/número de cuenta y comportamiento de gauges.
  • Validar las dos capas, su integración y representación desktop antes de declarar entrega completa.

Candidatos locales: backend f01ff4a (251 líneas); frontend 3fcd10d (352 líneas sobre backend). Evidencia local: 182 tests Rust pasan/1 ignorado para backend; 65 focales frontend y typecheck/suite/build pasan. No equivale a validación desktop ni a integración en main.

Fuera de alcance: persistir la opción showResets, clipping/backdrop, auto-hide, instalación, credenciales y nuevas integraciones.

Alternatives considered

Inferir vigencia desde OAuth exp o predecir resets desde porcentajes: descartado por mezclar conceptos. Mantener la metadata únicamente en backend no permite al usuario verla; las dos PRs forman una entrega funcional.

Dominant language
TypeScript
Stars
10
Forks
2
Avg merge
2h 45m
Merged PRs (30d)
75

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 egdev6/quorb

All issues in egdev6/quorb

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.