Qoder

New users receive a one-time 14-day Pro trial when they first sign in to the latest Qoder client, with 300 credits and all Pro features, including Quest, Repo Wiki and Experts Mode. The trial is limited to one account per user and is not available on virtual machines. When it ends, the account drops to Free and unused trial credits are cleared.

Upgrading before the trial ends converts the remaining trial credits into an add-on pack that keeps its original expiry date. Staying on Free keeps basic models with daily and monthly limits, limited completions and next edits, and the option to bring your own API key, so light work can continue without paying.

Credits are charged by model and by input and output tokens, so an agent request that calls several models costs more than a quick question. Qoder publishes median estimates from its own usage data, and it says actual deductions vary. Failed model requests do not deduct credits, and credits expiring soonest are used first.

• Editor Ask Mode: about 3 credits per request at 50K context, 4 at 200K.
• Editor Agent Mode: about 7 credits at 50K context, 12 at 200K.
• Qoder Agent Mode and Quest Agent Mode: about 50 credits per request.
• Quest Experts Mode: about 75 credits per request.
• Repo Wiki: about 50 credits per repository.

Editorial assessment

Choose the plan by agent mode, not by the number of files you edit. Qoder recommends Pro for everyday completion with light agent help, Pro+ for heavy autonomous agent work and Ultra for frequent long-running Quest tasks. At the published medians, Pro covers roughly 40 Quest Agent requests a month before falling back to basic models.

Credit Packs cost $20 for 1,500 credits and expire one month after purchase, which makes them more expensive per credit than the plan allowance. If you buy a pack most months, compare it with the next tier: Pro+ gives 6,000 credits for $60, while Pro plus two packs gives 5,000 for the same money.

Several offers change the numbers you see in September 2026. A first monthly purchase of Pro or Pro+ between September 1 and 30 (Singapore time) receives bonus credits equal to the plan amount, so Pro shows 4,000 credits in the first month. Renewals and upgrades in the same window receive 1,000 bonus credits, valid for 30 days.

Since September 18, individual users can claim 100 credits a day in the desktop app, each valid for 30 days, with no end date announced. The Qwen3.8-Flash model also costs no credits for a limited time, extended past September 30. Teams and Enterprise plans are excluded from all three, so budget on the standard allowance.

Under the terms you keep rights in your inputs and Qoder assigns you its rights in outputs, but you grant a worldwide license to use your content to operate and improve the services and develop new products. You can stop this for new content by turning off the Share and Improve setting; the privacy policy says the opt-out depends on your plan.

The privacy policy keeps de-identified content for research and product improvement for up to five years and shares prompts and code with outside model providers to generate outputs. Content may be processed outside your country. In Teams and Enterprise, admins can enable or disable Share and Improve centrally, which is the safer route for company code.

Individual plans bill monthly on the date you subscribed and renew one day before the cycle ends. If a renewal payment fails, the account returns to Free and unused credits are lost. Cancelling keeps the plan until the end of the period; Qoder does not support immediate downgrades within a period.

An upgrade takes effect at once and refunds the remaining value of the old plan’s credits, but it cannot be reversed and leftover credits do not carry over. A refund of a new subscription is possible only within 24 hours and before any credits are used, by emailing the account and bill to refund@qoder.com; Credit Packs are not refundable.

1. Record the client version, the model selected and the trial credit balance.
2. Send one Agent Mode request describing the endpoint and the test.
3. Review the diff and run the test suite locally.
4. Ask for one correction if a test fails, then run the suite again.
5. Record the credits used by each request on the Usage page.

Accept a change limited to the route and test files, a passing suite and a credit cost close to the published Agent Mode median. Reject edits to unrelated files, removed tests or a charge far above the estimate. No diff, test result or credit figure is reported until the exercise is run.

For an editor built around the same agent workflow, compare Cursor. For completions inside an existing editor, see GitHub Copilot, and for JetBrains-first teams, JetBrains AI Assistant.