Codex: Usage Dashboard opens ChatGPT home page (retired /codex/settings/usage route)

[RowboTony]

Version

CodexBar 0.66.0, macOS 15.7

Bug

In the Codex tab, clicking Usage Dashboard opens https://chatgpt.com/codex/settings/usage. That route no longer exists: ChatGPT redirects it to the home page (https://chatgpt.com/), not to any usage or settings page.

Expected

Open the Codex usage page. Two current pages work:

• https://chatgpt.com/codex/cloud/settings/analytics#usage (Codex → Settings → Analytics → Usage: weekly limit, credits, limit resets, usage charts)
• https://chatgpt.com/settings/usage (ChatGPT → Settings → Usage, redirects to ?tab=overview)

Cause

CodexProviderDescriptor still hardcodes dashboardURL: "https://chatgpt.com/codex/settings/usage". In 2bea4f0 ("Fix OpenAI web dashboard handoff") the OpenAI web scraper's usageURL moved to https://chatgpt.com/codex/cloud/settings/analytics#usage, but the menu's dashboard link wasn't updated. docs/codex.md and docs/providers.md also still list the old URL for the web dashboard.

Suggested fix

Point the descriptor's dashboardURL at https://chatgpt.com/codex/cloud/settings/analytics#usage, the same page the web scraper already loads. I have a PR ready.

[clawsweeper]

Codex review: this still needs some work. Reviewed September 25, 2026, 4:42 PM ET / 20:42 UTC.

Summary
The issue describes a current Codex menu-link bug. The same obsolete URL is present in the latest release and on current main. A linked, open PR specifically addresses it, so the issue should remain open until that PR is resolved.

Reproducibility: yes. for the menu-link path: current source passes the old URL to the browser, and the issue plus linked PR report the signed-in redirect to ChatGPT home. I did not run an independent browser check.

Root-cause cluster
Relationship: canonical
Canonical: #4004
Summary: The open linked PR is the candidate fix for this issue.

Members:

• fixed_by_candidate: fix(codex): open usage analytics from Usage Dashboard #4005 - Its body explicitly links this issue and its patch changes the exact menu URL reported here.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Next step
The open linked PR already owns the bounded repair, so a second fix PR is unnecessary.

Review details

Best possible solution:

Keep the menu destination and documentation aligned with the Codex analytics page, with a focused descriptor regression test.

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

Yes for the menu-link path: current source passes the old URL to the browser, and the issue plus linked PR report the signed-in redirect to ChatGPT home. I did not run an independent browser check.

Is this the best way to solve the issue?

Yes. Updating the descriptor and stale documentation to match the scraper’s existing analytics destination is a narrow fix, and the linked PR adds a focused regression test.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against ce1b80863e4b.

Label changes

Label changes:

• add P2: A broken secondary navigation action affects Codex users, while usage data remains available in CodexBar.
• add impact:ux-friction: Usage Dashboard sends users to the ChatGPT home page instead of the intended usage view.
• add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
• add clawsweeper:source-repro: Current issue advisory state selects this label.
• add clawsweeper:linked-pr-open: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.

Label justifications:

• P2: A broken secondary navigation action affects Codex users, while usage data remains available in CodexBar.
• impact:ux-friction: Usage Dashboard sends users to the ChatGPT home page instead of the intended usage view.

Evidence reviewed

What I checked:

• Current menu URL: The Codex provider descriptor still supplies the retired settings/usage URL. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:65, ce1b80863e4b)
• Menu call path: Usage Dashboard maps to openDashboard, which resolves provider metadata and passes the URL to NSWorkspace. (Sources/CodexBar/StatusItemController+Actions.swift:354, ce1b80863e4b)
• Existing analytics destination: The OpenAI web dashboard fetcher already loads the requested Codex analytics URL. (Sources/CodexBarCore/OpenAIWeb/OpenAIDashboardFetcher.swift:22, ce1b80863e4b)
• Documentation mismatch: The Codex documentation still prints the obsolete destination. (docs/codex.md:132, ce1b80863e4b)
• Shipped behavior: The v0.66.0 release contains the same old descriptor URL and menu-opening path; the fix is not present in that release. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:65, e665cbf64976)
• Linked fix candidate: The same-author PR at fix(codex): open usage analytics from Usage Dashboard #4005 is open and unmerged. Its patch changes the descriptor URL, adds a regression test, and updates the two affected documentation pages; its body explicitly links this issue and reports a signed-in browser check. (41ad05db3515)

Likely related people:

• Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• Ratul Sarna: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

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.

[steipete]

Fixed on main via #4005 by @RowboTony and shipping in 0.67.1: the Usage Dashboard action now opens the analytics usage page CodexBar's web scraper already uses instead of the retired settings route, with a registry-level regression test on the URL.