[Feature]: dashboard management gaps — delete rollback entries, custom usage ranges, rename account selectors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- full-stack
Research direction
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.
Written by the indexing model from the issue text.
Description
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?
- 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.
- Accept a user-selected start/end range on the Usage page with hourly granularity, and scope the existing cost estimate to that range.
- 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.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 4h 24m
- Merged PRs (30d)
- 574
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
添加全局代理功能Openenhancement proxy
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
bug tools
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement proxy
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lidge-jun/opencodex#6604 · 1 comment ·
Maintainers usually reply within 1 day
-
bug cli platform service
Difficulty 3/5 1-2 days Newbie friendliness 65/100
lidge-jun/opencodex#6575 · 2 comments ·
Maintainers usually reply within 1 day
-
bug proxy
Difficulty 5/5 Over a week Newbie friendliness 35/100
lidge-jun/opencodex#6568 · 3 comments ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
level/task reporter/qa type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wazuh/wazuh-dashboard-plugins#9310 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cybersemics/treecrdt#267 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
wiz-sec-public/backstage-plugin-wiz#16 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day