You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not report issues when pass-through is enabled; pass-through sends content as-is and does not go through new-api processing logic.
State facts and evidence concisely. Do not paste unfiltered AI-generated text in the issue body or in later comments.
Relay reports must first establish that the issue occurs in the new-api layer. Use equivalent redacted requests to compare the direct upstream result with the result through new-api, including response status, error body, and server logs. Reports that skip this comparison or only show an upstream error are not accepted.
Reports about Coding Plan services, reverse-engineered channels, third-party API wrappers, or compatibility issues caused by exposing a Codex endpoint through a reverse proxy as a general-purpose API are not accepted. Protocols or behavior specific to the Codex API should not be treated as standard OpenAI API behavior; confirm such issues with the channel or API provider first.
This project does not operate an official hosted service or provide technical support for third-party hosting sites, relay services, or API services. Contact the relevant operator for those issues.
Warning: issues with this template removed, section headings deleted, or content cleared may be closed directly. Repeated submissions of unfiltered AI-generated text, or repeated abusive submissions, may result in a block.
Non-duplicate issue: I have searched existing Issues and confirmed there are no similar issues.
Read this first: I have fully read the section above, reviewed the docs at https://docs.newapi.ai/ and the project README, and asked AI first, confirming this is not a usage, configuration, or integration question.
Supported version: I have provided an exact version, commit, or image tag (not latest or unknown) and confirmed that the issue reproduces on an unmodified, supported version from this repository.
Not a third-party service: I confirm that this issue is not exclusive to a third-party hosting site, relay, API service, or fork that has not been verified against the unmodified repository. Third-party instance issues must be reported to their operator.
Not pass-through: I confirm that pass-through is not enabled on the relevant channel. Pass-through sends content as-is and does not go through new-api processing logic; such reports are not accepted.
Issue attribution: I have provided evidence that distinguishes the client, new-api, and upstream layers. For relay issues, I compared equivalent redacted requests sent directly upstream and through new-api, confirming that new-api introduces or changes the error rather than merely forwarding the upstream error unchanged.
Channel and protocol boundary: I confirm that the issue is not caused by a Coding Plan service, reverse-engineered channel, third-party API wrapper, Codex reverse-proxy endpoint, or behavior specific to the Codex API. If first observed through such an interface, I have reproduced it using a standard API protocol supported by this repository.
Maintainer time: I understand that maintainers have limited time. Do not paste unfiltered AI-generated text in the issue body or in later comments; extract the points needed for review first. Submissions that do not follow this template, or that omit the necessary points and cannot be reviewed, may be ignored or closed. Repeated submissions of this kind may result in a block.
Issue Description
Actual behavior: the Billing History dialog (/wallet, Order History) shows the top-up status as Success, Pending or Expired in every language. In Simplified Chinese it should read 成功, 待确认, 已过期.
Cause: web/src/features/wallet/components/dialogs/billing-history-dialog.tsx passes statusConfig.label from getStatusConfig straight to StatusBadge without t(). The keys already exist in all seven locales.
Impact: every non-English user sees English statuses in their billing history.
Frequency: always.
Frontend details: /wallet, Order History, Billing History dialog. Headless Chromium 141.0.7390.37, light theme. No app errors in the console.
Steps to Reproduce
Switch the interface language to 简体中文.
Open /wallet and click Order History.
The status column reads Success / Pending / Expired.
Expected Result
成功 / 待确认 / 已过期 in Chinese, and the matching translation in the other languages.
Read This First
Deployment source
Repository main branch source (self-built)
Your current newapi version
main at 789c970. Same code in v1.0.0-rc.40.
Submission Checks
latestorunknown) and confirmed that the issue reproduces on an unmodified, supported version from this repository.Issue Description
Actual behavior: the Billing History dialog (
/wallet, Order History) shows the top-up status asSuccess,PendingorExpiredin every language. In Simplified Chinese it should read成功,待确认,已过期.Cause:
web/src/features/wallet/components/dialogs/billing-history-dialog.tsxpassesstatusConfig.labelfromgetStatusConfigstraight toStatusBadgewithoutt(). The keys already exist in all seven locales.Impact: every non-English user sees English statuses in their billing history.
Frequency: always.
Frontend details:
/wallet, Order History, Billing History dialog. Headless Chromium 141.0.7390.37, light theme. No app errors in the console.Steps to Reproduce
/walletand click Order History.Success/Pending/Expired.Expected Result
成功/待确认/已过期in Chinese, and the matching translation in the other languages.Related Screenshots
No response