Help
Feedback and contact
Tell us about errors, wrong charges, or features you want. Valid bugs and adopted suggestions earn credit.
Key points
- Signed in, report it on the console's Feedback page; it attaches your latest requests, and shows progress and rewards.
- For live chat, add our support on WeChat,
LianGZiJian_JJ, and they will add you to the user group. - For refunds, appeals, account data and security issues, message our WeChat support privately; never post order numbers or keys in the group.
- Include the time of the error and its usage log entry; that is the fastest way for us to find it.
- A valid bug earns $5–$20 in credit, a billing error or security vulnerability from $50, an adopted suggestion $5.
How to reach us
| Topic | Where |
|---|---|
| Errors, charge problems, feature suggestions | The console's Feedback page, preferred |
| Usage questions, live chat | The WeChat group: add our support, LianGZiJian_JJ, to join |
| Refunds, wrong charges, account appeals, data deletion | A private message to our WeChat support |
| Security vulnerabilities | A private message to our WeChat support only, never in the group |
Before reporting an error, check Service status: if there is an incident, we are already on it. Common errors are explained in Errors and the FAQ.
Writing a report
The more of this you include, the faster we find the cause:
- When it happened, to the minute.
- The usage log entry: find the failed request in the console's Usage Logs and capture its model, status and cost.
- The exact error message, as copied text rather than a screenshot.
- Your setup: the client (Claude Code CLI, CC Switch, Magpie, VS Code or JetBrains), the output of
claude --version, and your operating system. - Steps to reproduce: what you did, what you expected, what happened, and whether it happens every time.
- For an account matter in a private message, add your account email; for a refund, also the top-up order number.
Never send a full API key. To identify a key, give its name or the first few characters shown in the console.
Feedback rewards
| Type | Reward |
|---|---|
| Valid bug: reproducible and confirmed by us | $5–$20 in credit, by impact |
| Serious issue: billing error, security vulnerability | From $50 |
| Adopted suggestion | $5 in credit |
- For the same issue, the reward goes to the first person who reports it.
- The issue must be reproducible, or come with enough detail for us to find it. Known issues already posted on Service status or in an announcement are not rewarded again.
- CoreCode decides whether a report is valid and how much it earns. A reward for a report filed in the console goes straight to your balance; one reported in the group arrives as a redemption code in a private message, to redeem on the Wallet page.
- Report security vulnerabilities privately only. Public disclosure, or exploiting a vulnerability to gain credit or reach other users' data, earns no reward and is handled under the terms of service.
- When you are overcharged, the excess returns to your balance in full under the terms of service; the reward comes on top.