fix(codex): open usage analytics from Usage Dashboard

[RowboTony]

Summary

Fixes #4004. Codex's Usage Dashboard action opens https://chatgpt.com/codex/settings/usage, which ChatGPT now redirects to the home page. It now opens https://chatgpt.com/codex/cloud/settings/analytics#usage, the Codex usage analytics page that OpenAIDashboardFetcher.usageURL has loaded since 2bea4f0.

• CodexProviderDescriptor: update dashboardURL. This is provider metadata only; the scraper, isUsageRoute, auth, and fetching are unchanged.
• Add a CodexProviderDescriptorTests regression test, mirroring OpenRouterProviderDescriptorTests.
• docs/codex.md and docs/providers.md: the web-dashboard URL now matches what the scraper actually loads.
• CHANGELOG entry under 0.67.0 → Fixed.

Verification

• Freshly built app (real behavior): packaged this branch with ./Scripts/package_app.sh debug (CodexBar 0.67.0, com.steipete.codexbar.debug, ad-hoc signed) on macOS 15.7.9 and launched it. In the Codex tab, Usage Dashboard opened https://chatgpt.com/codex/cloud/settings/analytics#usage in the browser, landing on Codex and Work Analytics › Usage with the same weekly limit as the menu. Hide personal information was enabled for the capture. Before the fix, v0.66.0 opens chatgpt.com/codex/settings/usage, which lands on chatgpt.com/ (home).
• Regression test: swift test --filter CodexProviderDescriptorTests passes on this branch (1 test, 1 suite). With main's descriptor restored, it fails with dashboardURL → "https://chatgpt.com/codex/settings/usage".
• Toolchain: Xcode 26.3 / Swift 6.2.4 (the newest Xcode for macOS Sequoia). Building the test bundle on Swift 6.2 needed a local-only split of one expression in TestsLinux/CostUsageQuotaWeekLinuxTests.swift (lines 245 and 288 hit "unable to type-check this expression in reasonable time"). That tweak is not part of this PR; I can send it separately if useful.
• make check: my changes are clean. The only violation is a pre-existing line_length in Sources/CodexBarCore/Providers/TypeSafe/TypeSafeWebFetchStrategy.swift:175 on main, which this PR doesn't touch.

After: Usage Dashboard in the freshly built app (0.67.0)

After: the page it opens

🤖 Generated with Claude Code

https://claude.ai/code/session_01U5RPHRnyM31gn2f7XjM4aw

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 26, 2026, 2:11 AM ET / 06:11 UTC (Revision 6).

ClawSweeper review

What this changes

Updates CodexBar’s Codex Usage Dashboard link to open usage analytics, with a regression test, documentation updates, and an unreleased fix note.

Merge readiness

✅ Ready for maintainer review

Current main and v0.67.0 still open the retired Codex dashboard route. This paired PR addresses the reported problem, has direct screenshot evidence of the new destination, and has no identified blocking defect.

Priority: P2
Reviewed head: 4cdfbc62930697c2e2b1ec735ae9c2a665101921

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	A focused repair with registered-metadata coverage and convincing app-to-browser visual proof.
Proof confidence	🦞 diamond lobster (5/6) ✨ media proof bonus	Sufficient (screenshot): The changed provider URL feeds the menu’s browser action; the contributor reports exercising that action in a freshly packaged macOS build, and supplied screenshots show the selected action and the resulting Codex usage page. No stored-data contract changes.
Patch quality	🦞 diamond lobster (5/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Verified	Sufficient (screenshot): The changed provider URL feeds the menu’s browser action; the contributor reports exercising that action in a freshly packaged macOS build, and supplied screenshots show the selected action and the resulting Codex usage page. No stored-data contract changes.
Evidence reviewed	8 items	Introduced patch: The pinned main-to-head diff changes the Codex dashboard URL, adds a registered-metadata test, updates two docs pages, and adds an unreleased fix note. Menu routing: The dashboard action resolves the selected provider’s metadata URL and opens it with NSWorkspace. Existing analytics route: The OpenAI web fetcher already loads the same Codex analytics URL; the PR does not change fetching or route recognition.
Findings	None	None.
Security	None	None.

How this fits together

CodexBar’s menu reads the selected provider’s dashboard URL from registered metadata and opens it in the system browser. Its separate OpenAI web fetcher already uses the analytics page to collect Codex usage.

flowchart LR
  A[Codex menu] --> B[Usage Dashboard action]
  B --> C[Registered provider URL]
  C --> D[System browser]
  D --> E[Codex usage analytics]
  F[OpenAI web fetcher] --> E

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Root-cause cluster

Relationship: fixed_by_candidate
Canonical: #4004
Summary: This PR is the open candidate fix for the paired dashboard-routing issue.

Members:

• canonical: Codex: Usage Dashboard opens ChatGPT home page (retired /codex/settings/usage route) #4004 - The issue describes the same retired menu route and explicitly points to this fix.

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

Technical review

Best possible solution:

Keep the menu destination aligned with the working Codex analytics route and ship the focused regression coverage in the next release.

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

Yes. v0.67.0 and current main register the retired URL, and the menu action opens that registered URL; the contributor reports its redirect to the home page. I did not execute current main.

Is this the best way to solve the issue?

Yes. Changing the registered menu URL to the analytics page already used by the fetcher is a narrow repair, and the new test covers that registration.

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

No label changes.

Label justifications:

• P2: The broken dashboard shortcut causes limited user-facing friction, and this PR supplies a bounded fix.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (screenshot): The changed provider URL feeds the menu’s browser action; the contributor reports exercising that action in a freshly packaged macOS build, and supplied screenshots show the selected action and the resulting Codex usage page. No stored-data contract changes.
• proof: sufficient: Contributor real behavior proof is sufficient. The changed provider URL feeds the menu’s browser action; the contributor reports exercising that action in a freshly packaged macOS build, and supplied screenshots show the selected action and the resulting Codex usage page. No stored-data contract changes.
• proof: 📸 screenshot: Contributor real behavior proof includes screenshot evidence. The changed provider URL feeds the menu’s browser action; the contributor reports exercising that action in a freshly packaged macOS build, and supplied screenshots show the selected action and the resulting Codex usage page. No stored-data contract changes.

Evidence

What I checked:

• Introduced patch: The pinned main-to-head diff changes the Codex dashboard URL, adds a registered-metadata test, updates two docs pages, and adds an unreleased fix note. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:62, 4cdfbc629306)
• Menu routing: The dashboard action resolves the selected provider’s metadata URL and opens it with NSWorkspace. (Sources/CodexBar/StatusItemController+Actions.swift:348, 4cdfbc629306)
• Existing analytics route: The OpenAI web fetcher already loads the same Codex analytics URL; the PR does not change fetching or route recognition. (Sources/CodexBarCore/OpenAIWeb/OpenAIDashboardFetcher.swift:22, 4cdfbc629306)
• Current-main gap: The fetched main revision still registers the retired /codex/settings/usage URL, so the central fix is not yet on main. (Sources/CodexBarCore/Providers/Codex/CodexProviderDescriptor.swift:65, 3d2364346da8)
• Release check: The latest release, v0.67.0, also contains the retired menu URL; this fix is recorded under 0.67.1 Unreleased on the PR branch. (CHANGELOG.md:3, e0286a895055)
• Regression coverage: The new test checks the URL obtained from registered Codex metadata, including its usage fragment. (Tests/CodexBarTests/CodexProviderDescriptorTests.swift:8, 4cdfbc629306)

Likely related people:

• steipete: 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)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• 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.

History

Review history (5 earlier review cycles)

• reviewed 2026-09-25T20:43:36.103Z sha 41ad05d :: needs real behavior proof before merge. :: none
• reviewed 2026-09-26T01:24:00.636Z sha 41ad05d :: blocked before merge. :: [P2] Move this fix into the unreleased 0.67.1 notes
• reviewed 2026-09-26T02:46:42.634Z sha 1420143 :: needs maintainer review before merge. :: none
• reviewed 2026-09-26T04:21:44.367Z sha daa9c1a :: needs maintainer review before merge. :: none
• reviewed 2026-09-26T05:53:49.797Z sha cf6b15a :: needs maintainer review before merge. :: none

[steipete]

Merged as yours, @RowboTony, with your commits intact; the maintainer commits on your branch only added the URL regression test, the doc updates, the changelog line, and merges from main. Ships in 0.67.1. Thanks for the fix, and welcome aboard.