[Feature]: dashboard management gaps — delete rollback entries, custom usage ranges, rename account selectors

Chiusa
  • Qualcosa non va?
#3,379 4 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
full-stack

Direzione di ricerca

Start by reading the existing restore flow in src/server/management/integration-routes.ts, gui/src/pages/integrations/RollbackHistory.tsx, and src/integrations/journal.ts. Then inspect gui/src/pages/Usage.tsx, src/usage/summary.ts, gui/src/components/CodexAccountPickerSetting.tsx, and src/server/management/config-routes.ts. Done means the dashboard supports safe rollback deletion, arbitrary hourly usage ranges with scoped estimates, and local account-label editing.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement gui priority: P3
Area

Dashboard

What are you trying to accomplish?

Manage the things the dashboard already displays. Three reports describe the same gap from different pages: the data is visible, the control is missing. Each is closed individually and absorbed here:

  • #2399 (@ncepuee) — delete old "restore to this point" snapshots in the integrations UI
  • #2748 (@areskts) — custom date/hour usage ranges with cost estimates（按日期、小时维度自定义查询并估算价格）
  • #3017 (@hayabusasxs) — edit Codex account selector names
What prevents this today?

Rollback history is read-only. src/server/management/integration-routes.ts exposes the journal as GET only, and gui/src/pages/integrations/RollbackHistory.tsx renders restore and expired states with no delete affordance. src/integrations/journal.ts deliberately preserves journal rows while pruning snapshot files, so entries accumulate and the operator cannot clear them.

Usage ranges are fixed. gui/src/pages/Usage.tsx offers 7d / 30d / all only. Estimated cost totals exist (src/usage/summary.ts), but they cannot be scoped to an arbitrary interval, and there is no hourly bucketing.

Account selector names are display-only. gui/src/components/CodexAccountPickerSetting.tsx toggles codexAccountPickerEnabled and nothing else; src/server/management/config-routes.ts returns picker visibility and exposes no rename API. Operators running several accounts cannot label them meaningfully.

What should OpenCodex do?
  1. Allow deleting a rollback journal entry from the integrations UI, with the same safety the restore path already has, and state clearly whether the underlying snapshot is already gone.
  2. Accept a user-selected start/end range on the Usage page with hourly granularity, and scope the existing cost estimate to that range.
  3. Provide a rename API for Codex account selector labels and an editor in the dashboard, keeping the label local and never sending it upstream.
Example usage or interface
Usage  [ 2026-08-01 00:00 ] → [ 2026-08-03 12:00 ]   granularity: hour
  estimated cost over range: $12.40

# rename is local metadata only
PATCH /api/config/codex/accounts/<id>  { "displayName": "team-billing" }
Alternatives or workarounds

Operators edit configuration files by hand or read raw request history, which is what a dashboard exists to prevent.

Additional context

Absorbs #2399, #2748, #3017. Credit for the original analysis belongs to @ncepuee, @areskts, and @hayabusasxs.

Checks
  • I searched existing issues and documentation.
  • This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
  • I removed secrets and personal data.
Lingua principale
TypeScript
Stelle
16.9k
Fork
1.3k
Merge medio
16h 51m
PR unite (30g)
681

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lidge-jun/opencodex

Tutte le issue di lidge-jun/opencodex

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.