Usage Dashboard does not open the correct website

[igneous-prose]

For Codex, when selecting 'Usage Dashboard' in the top menu bar, it redirects to https://chatgpt.com.

[clawsweeper]

Codex review: this still needs some work. Reviewed September 26, 2026, 5:03 PM ET / 21:03 UTC.

Summary
The reported redirect matches a previously fixed Codex menu-link bug. Current main uses the corrected URL, but v0.67.0 does not contain the fix, and this repository’s onboarding policy does not permit automatic closure.

Reproducibility: no. current-main reproduction is established: its menu URL is corrected. The earlier report and fix patch establish the old route that affected builds before the fix.

Root-cause cluster
Relationship: duplicate
Canonical: #4004
Summary: The earlier closed issue describes the same Codex Usage Dashboard redirect and links the merged fix.

Members:

• canonical: Codex: Usage Dashboard opens ChatGPT home page (retired /codex/settings/usage route) #4004 - It names the retired URL and redirect and was closed after the fix merged.
• fixed_by_candidate: fix(codex): open usage analytics from Usage Dashboard #4005 - This merged PR changes the exact URL used by the menu action.

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

Maintainer decision needed

Question	Recommendation
Should this report stay open until the 0.67.1 release and a retest, or be resolved as fixed on main now?	Keep through release: Track the report until 0.67.1 ships and the reporter can retest the installed app.

Why: The fix is merged but unshipped, and the repository profile reserves closure for maintainer judgment.

Next step
A merged fix already owns the code change; maintainer release judgment and an installed-version retest remain.

Review details

Best possible solution:

Ship the existing URL fix in 0.67.1, retain its regression test, and confirm the reporter’s installed version and result after updating.

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

No current-main reproduction is established: its menu URL is corrected. The earlier report and fix patch establish the old route that affected builds before the fix.

Is this the best way to solve the issue?

Yes. Reusing the analytics URL already used by CodexBar’s web dashboard is a narrow repair, and the merged change includes a descriptor regression test.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The reporter did not identify their installed version; v0.67.0 predates the fix, so a release and retest are needed to distinguish shipped behavior from current main.

Codex review notes: model internal, reasoning medium; reviewed against c1f50ac13749; fix evidence: commit 41ad05db3515, main fix timestamp 2026-09-25T20:37:42Z.

Label changes

Label changes:

• add P2: The shipped menu link can send Codex users to the wrong page, while the rest of the app remains usable.
• add impact:ux-friction: Users must navigate from the ChatGPT home page to find the intended usage view.
• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:not-repro-on-main: Current issue advisory state selects this label.

Label justifications:

• P2: The shipped menu link can send Codex users to the wrong page, while the rest of the app remains usable.
• impact:ux-friction: Users must navigate from the ChatGPT home page to find the intended usage view.

Evidence reviewed

What I checked:

• Current URL: The Codex provider metadata now points to the analytics usage page. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:62, c1f50ac13749)
• Menu path: The menu action resolves the selected provider's dashboard URL and opens it through macOS. (Sources/CodexBar/StatusItemController+Actions.swift:348, c1f50ac13749)
• Regression coverage: A focused test asserts the registered Codex URL and its usage fragment. (Tests/CodexBarTests/CodexProviderDescriptorTests.swift:7, c1f50ac13749)
• Fix provenance: The commit patch replaces the retired settings URL with the current analytics URL. GitHub identifies its author as RowboTony. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:62, 41ad05db3515)
• Merged fix: The same-repository pull request explicitly addresses the retired URL and was merged on 2026-09-26. (0fdf759a451c)
• Release boundary: No tag contains the fix commit; current CHANGELOG.md places it under 0.67.1 Unreleased, while v0.67.0 is the latest identified release. (CHANGELOG.md:26, c1f50ac13749)

Likely related people:

• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; confidence: low)
• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; 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.