Codex Desktop: add payment-method change at upgrade checkout and one-click restart guidance

Open
#34,536 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop, payments

Research direction

Start with the existing profile-menu and direct Codex upgrade entry points, then review the linked interactive prototype and one-page UX specification. Trace the current plan-confirmation dialog and payment-management return flow before assessing the restart path. Done means the acceptance criteria hold across payment changes, recalculated totals, restart handling, reduced motion, and duplicate-action prevention.

Written by the indexing model from the issue text.

Description

app enhancement windows-os

Summary

Let users change the selected payment method from the plan confirmation dialog, then clearly offer Restart Codex when a restart is required to display the updated usage limit.

Problem

On Windows, the plan confirmation dialog displays the current payment method beside Pay now, but provides no Change action. Updating the method requires leaving checkout, finding Settings > Billing, making the change, and returning to the upgrade flow.

The same issue exists whether checkout is opened directly from Codex or reached through Upgrade for more usage in the existing profile menu. This request does not propose adding a permanent billing item to that menu.

After the plan change succeeds, the usage limit shown in Codex may require an app restart before it updates. The interface provides no instruction or restart button, so users have to discover and perform the restart manually.

Proposed UX

  • Keep the existing profile menu unchanged.
  • Use the same improved confirmation dialog from both existing upgrade entry points.
  • Right-align the masked payment method in the payment row.
  • Place Change directly below the masked last-four example.
  • Reuse the authoritative payment-management surface and preserve the selected plan, proration, tax, and total when the user returns.
  • Revalidate payment method and totals before purchase.
  • Apply the updated usage limit automatically when possible.
  • Acknowledge the successful upgrade with a brief, non-blocking check-and-spark motion.
  • When a restart is required, show one compact message: You're all set. Restart Codex once to load your new usage limit.
  • Provide Restart Codex as the primary action and Later as the secondary action.
  • Avoid repeating the same status in a title, checklist, body paragraph, and footer.
  • After restart, show the account-sourced updated usage limit.

Acceptance Criteria

  • The profile menu gains no permanent billing or payment item.
  • Checkout exposes a separate Change action directly below the right-aligned masked card digits.
  • Returning from payment management preserves the upgrade context and recalculates totals.
  • A successful plan change is not mislabeled as delayed or failed.
  • A required restart is explained immediately and can be completed with one click.
  • The success animation plays once, never blocks interaction, and respects reduced-motion preferences.
  • Completion copy remains concise and non-repetitive.
  • Purchase and restart actions cannot be submitted twice.
  • Sensitive payment data is not exposed beyond a minimal masked label.

Evidence Boundary

This request reflects an observed Windows journey in which restarting Codex makes the updated usage limit appear. It does not claim that payment was delayed, that entitlement propagation failed, or that the account encountered a quota outage.

Prototype

Current confirmation state:

Current confirmation state

Proposed payment-method action:

Proposed payment-method action

Existing profile entry point, intentionally unchanged:

Existing profile entry point

Proposed one-click restart instruction:

Proposed one-click restart instruction

The reporter's source screenshots are not included. The prototype uses generic labels and invented card digits, with no real name, email, address, project names, or account values.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.