Contact and Feedback

Hit a problem, have a feature request, or want to reach the team directly? See whether you can resolve it yourself first, and if you still need help, contact us through any of the channels below.

Before you file

The FAQ covers common questions and the Error Reference explains common server-side errors — worth checking before you reach out.

A few quick self-checks often resolve things on the spot:

• Is the CLI up to date? (run kimi --version, and update if needed)
• Can you reach Kimi's service? A corporate network or proxy may block api.kimi.ai
• Are you signed in, and is your API Key valid?
• Are the current working directory and file permissions OK?

Feedback channels

Still stuck, or want to share a feature request or feedback? Pick whichever channel below fits.

Online support

Go to Kimi.ai on the web, click your profile picture in the bottom-left corner, then select Get Help → User Feedback to reach our support team. Product usage, bugs, quota, and refund questions are all handled here — please describe the problem, the steps you took, and any relevant logs.

Report from the CLI (recommended)

Run /feedback in the Kimi Code CLI interactive UI, then choose what to upload alongside your report:

• No attachment — text feedback only
• Logs only — wire events and diagnostic logs from this session; pick at least this so we have something to triage
• Logs + codebase — also includes your codebase for deeper diagnosis; sensitive files (.env, config files, secret keys) are automatically excluded, and attachments are used only for diagnosis and never shared

After submitting, the CLI shows a Session and a Feedback ID. Email [email protected] with both to follow up.

GitHub Issues

Search existing issues or open a new one in the Kimi Code CLI repository:

• https://github.com/MoonshotAI/kimi-code/issues

Email

Email [email protected]. To help us triage quickly, please include:

• A description of the problem
• Steps to reproduce
• Environment info (run kimi --version)
• Relevant error logs — run /export-debug-zip in the CLI (or kimi export from the shell) to produce a debug ZIP that already bundles the diagnostic logs, and attach it.

Join the Discord community

Join our Discord community to chat with the team and other users.

Account appeals

If your account was mistakenly suspended or you need to report abuse, email [email protected] with your account ID, the time it occurred, and a brief description of the situation.