Repository navigation
[FEATURE]: Configure usage cost display currency #32485
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Usage costs are currently formatted as USD in the app and TUI. Users with custom model pricing may want to display costs in another currency, or may already configure model prices in a local currency.
Please add config for the displayed cost currency and the source currency used by configured prices, so examples like CNY display and RMB-denominated custom prices can be represented without double conversion.
Metadata
Metadata
Assignees
Labels
No labels
Activity
hugozhu commentedon Jun 16, 2026
support!
tianshan233 commentedon Jul 20, 2026
+1 from a Chinese user! Would love to see costs in CNY/RMB. Excited to see this feature being tracked!
tianshan233 commentedon Jul 20, 2026
By the way, I built a small tool for automating proxy setup via Mihomo/Clash during development. Might be useful for other Chinese devs: https://github.com/tianshan233/auto-proxy
Meinianda-L commentedon Aug 8, 2026
Opened a PR for this: #41208. It adds a
display.currencyconfig (with optionaldisplay.ratesoverrides) that converts displayed usage costs in the TUI, app, and ACP usage updates, while keeping the provider currency as the source value. The source-currency half of this issue (custom prices configured in RMB) is covered by the provider-levelcurrencyfield from #39425, which this PR builds on. Happy to adjust if @StarpTech is still actively working on this.iyhome commentedon Sep 25, 2026
+1 — I'd really like a configurable display currency.
For anyone looking into this, the cost is hardcoded to USD in two places:
packages/tui/src/component/prompt/index.tsx(the prompt status line):const money = new Intl.NumberFormat("en-US", { style: "currency", currency: "USD" })packages/tui/src/feature-plugins/sidebar/context.tsx(sidebar "Context" block): the same formatter.A minimal client setting would already cover the common case, e.g. in
cli.json:{ "cost": { "currency": "CNY", // display currency "locale": "zh-CN", "source_currency": "USD", // currency the provider/model prices are in "rate": 7.20 // source_currency -> currency } }Keeping
source_currency+rateseparate matters for users whose configured model prices are already in their local currency (e.g. DeepSeek bills in CNY), so a naive USD->CNY conversion doesn't double-convert. Defaults could stayUSD/en-US/1:1to preserve current behavior.Thanks!
feat: support configurable cost display currency