Summary
I purchased the Go plan on May 25, 2026 (invoice $1.34) specifically to test the API, then realized API access required an upgrade. I upgraded to Pro on May 26, 2026 — but the upgrade charged me the full $15 without any proration or deduction for the Go plan payment I made less than 24 hours prior. Additionally, the tokens I consumed yesterday under the Go plan are still being counted against my new Pro plan quota instead of being reset.
Expected Behavior
- When upgrading within the same billing cycle, the previous payment should be prorated or deducted from the upgrade cost.
- Token usage should reset when switching to a new plan tier.
Actual Behavior
- Full $15 charged on upgrade, with the $1.34 Go payment completely ignored.
- Tokens consumed under Go plan carried over and deducted from Pro plan quota.
Steps to reproduce
- Purchase Go plan ($1.34) on May 25, 2026
- Within 24 hours, upgrade to Pro plan
- Observe that $15 is charged in full with no credit for the Go payment
- Check token quota — yesterday's consumption is still deducted
Additional context
- Command Code username: dagezoo7cxv
- This was discussed on Discord with @ahmad Awais, who asked me to file a GitHub issue (ref: May 26, 2026 thread)
cmd feedback could not be run as cmd is not installed on this machine; filing manually instead
- Invoices:
- May 25, 2026 — Subscription invoice — Paid — $1.34
- May 26, 2026 — Subscription invoice — Paid — $15.00
Summary
I purchased the Go plan on May 25, 2026 (invoice $1.34) specifically to test the API, then realized API access required an upgrade. I upgraded to Pro on May 26, 2026 — but the upgrade charged me the full $15 without any proration or deduction for the Go plan payment I made less than 24 hours prior. Additionally, the tokens I consumed yesterday under the Go plan are still being counted against my new Pro plan quota instead of being reset.
Expected Behavior
Actual Behavior
Steps to reproduce
Additional context
cmd feedbackcould not be run ascmdis not installed on this machine; filing manually instead