The new Qoder CN documentation site is now available. Content on this site may not reflect the latest product features and changes. Visit docs.qoder.cn for the latest product documentation.
This document covers the new Credits subscription mechanism, effective from 12:00 (UTC+8) on May 20, 2026. For more details on pricing, see our billing information.
What are Credits?
Credits are the unit used to measure consumption when Qoder CN products call an AI model. They represent the computational resources consumed by a task. For example, in Qoder CN IDE, the following operations consume Credits:
Editor
Inline Chat
ask mode
agent mode
Quest
agent mode
experts mode
Knowledge Engine
RepoWiki
knowledge card
The actual consumption depends on the task's complexity and the AI model used.
Credit sharing for suite subscriptions
Credits from a Qoder CN suite subscription are shared across products as follows:
For Personal Free, Pro, and Pro+ plans: Credits can be used across Qoder CN Desktop, the JetBrains plugin, QoderWork CN, Qoder CLI CN, and Qoder CN Mobile.
For Teams and Enterprise VPC plans: Credits can currently be used across QoderWork CN and Qoder CLI CN. Support for IDE and the JetBrains plugin is coming soon.
Deduction rules
The system consumes Credits with the earliest expiration date first to help you maximize resource utilization.
Failed requests
You are not charged for failed AI model calls. Credits are deducted only for successful requests.
What happens when Credits are exhausted
When your Credits are exhausted:
Advanced models (agent mode, Quest, and other high-consumption features) will become unavailable
The system automatically switches to a basic model, continuing to provide limited capabilities such as basic code completion
How to restore access: Purchase a credit pack (takes effect immediately) or wait for the next billing cycle when Plan Credits reset
The Plan Credits reset cycle is based on your purchase date, not the calendar month. For example, if you purchased on July 5, the next reset will be on August 5. Unused Plan Credits do not carry over to the next cycle and are reset to zero. Add-on Credits have their own independent expiration date and are not reset with the subscription cycle.
View Credits usage
In-product usage
Desktop and JetBrains plugin: Click the Credits usage button in the bottom-right corner of the window to view your current usage.
QoderWork CN: Click the Credits usage button in the top-right corner of the application to view your current usage.
Qoder CN CLI: Run the built-in
/usageslash command to view your account's current Credits usage.
Usage on the website
You can view usage for QoderWork CN and Qoder CLI CN on the website.
Log in to the Qoder CN website, click your avatar in the top-right corner, and go to Settings > Usage to view your current plan information and the available balance and usage details for each type of Credit:
Plan Credits: These are the Credits included in your plan. They are valid for the current subscription cycle and are reset to zero at the end of the cycle.
Add-on Credits (credit pack): These Credits are acquired from purchases or promotional activities and are for personal use only.
Consumption priority: The system consumes Credits with the earliest expiration date first. If expiration dates are the same, Plan Credits are deducted before Add-on Credits.
Expiration date: Credits from different sources have different expiration dates, which you can find in the Credits log. Note that actions such as plan upgrades may shorten the expiration date. See the Credits log section for details.
Troubleshooting abnormal consumption
If you feel that your Credits are being consumed faster than expected, refer to the following common causes:
Agent mode consumes far more than Ask mode
Agent mode triggers multiple model calls in the background (tool calls, code modifications, validation, etc.). A single Agent request typically consumes 2 to 4 times more than Ask mode. Quest Experts mode coordinates multiple agents in parallel and has the highest consumption. If your daily use primarily involves conversational queries, we recommend using Ask mode to save Credits.
Larger context windows lead to higher consumption
Requests with a 200K context window consume more than those with a 50K window. If your project has many files and automatic context is enabled, actual consumption will be higher than the 50K reference values in the table above.
Retries and refreshes also consume Credits
Each retry or conversation refresh triggers a new model call and incurs a separate charge. Repeatedly retrying the same question accumulates consumption.
For simple tasks, disable thinking mode or switch to a lighter model
Thinking mode lets the model "think through" a problem before answering, which improves accuracy for complex questions but consumes additional tokens.
For simple tasks such as Q&A, format conversion, or information extraction that do not require deep reasoning, we recommend disabling thinking mode. Disabling it has virtually no impact on these tasks since they do not benefit from complex reasoning, and responses will be faster and more cost-efficient.
For complex tasks involving multi-step reasoning, code logic, or solution design, consider enabling thinking mode.
Different model sizes have different pricing. We recommend switching to a lighter model for simple tasks and starting a new conversation. How to identify lighter models? The Qoder model selector provides a relative consumption multiplier as a reference value, which is simulated by the Qoder product team based on specific task scenarios. Note: This value is not used as the actual deduction basis. Actual Credits deductions are based on the real service consumption generated by your requests.
When switching topics or models, start a new conversation
The context from an old conversation is carried forward into subsequent messages, even if it is no longer relevant, which increases model consumption. Starting a new conversation clears irrelevant context and starts fresh.
Looping consumption caused by system errors
If you encounter a situation where the client continuously displays "System busy" while the background keeps refreshing and Credits drop abnormally fast, this may be a system error. Please:
Immediately close the current conversation or exit the application
Report the issue through the feedback channel in the IDE or QoderWork
Include the time period and a description of the abnormal behavior so the team can investigate your usage
Credits log
The Credits log records the acquisition history of all your Credits, including the reason, amount, effective date, and expiration date. Common acquisition types include:
Description | Description |
Plan Credits | Credits included in your plan. |
Credit purchase | Purchase of a credit pack. |
The expiration date in the log is an initial estimate at the time of issuance. Actions like plan upgrades may cause the Credits to expire sooner. Refer to your plan change records for confirmation.
The Credits log only records acquisition information. To view your current available balance, go to the Credits card on the Usage page.
FAQ
Are Qoder CN Credits and Qoder Credits equivalent?
No. Qoder CN and Qoder have different pricing. The two types of Credits are not equivalent and cannot be used interchangeably.
Purchased a credit pack but it doesn't show on the usage page?
Make sure you are viewing the page that corresponds to your product line: the original Lingma is at qoder.console.alibabacloud.com, while the suite is at qoder.com.cn. Usage is not shared between the two. If you have confirmed the correct product line and the credits still do not appear, try signing out and signing back in.
Why can't I see my original Lingma subscription quota in QoderWork?
Because Credits from the original Lingma subscription do not take effect in QoderWork. QoderWork belongs to the suite product line, and you need a separate Qoder CN (suite) subscription to use paid features in QoderWork. For more details, see Credits.