try Kimi

This page covers common error codes and self-repair options for Kimi Claw.

Common error codes

CodeMeaningWhat to Do
400Bad Request — Malformed input or invalid parametersCheck your message for unsupported content, then retry.
401Unauthorized — Authentication failedSign out of Kimi and sign back in. If the issue persists, check your API credentials in Kimi Claw settings.
403Forbidden — Insufficient permissionsVerify your membership tier supports the feature you're using. Ensure your account isn't restricted.
429Too Many Requests — Rate limit exceededWait a few minutes and retry. See Conversation Limits for details on checking your quota.
500Internal Server Error — Something went wrong on the serverRetry after a short wait. If recurring, use the self-repair options below or contact support.

Self-repair options

Kimi Claw provides built-in repair tools accessible from Settings on the web:

OptionWhat It Does
Restart Kimi ClawRestarts the gateway connection. Fixes most transient issues (bridge disconnects, temporary hangs).
Repair Kimi ClawRuns an automated diagnostic that detects and fixes configuration problems. Try this when a simple restart doesn't help.
Restore Initial SettingsResets Kimi Claw to its default state. Workspace files and Memory are preserved, but chat platform connections (Telegram, etc.) need to be reconfigured. Use as a last resort.

Escalation path

If the self-repair options don't resolve the issue:

  1. Run /logs in the Terminal to capture recent error output.
  2. Run /debug to enable verbose diagnostics.
  3. Contact [email protected] with the error details and any relevant logs.
General troubleshooting - Kimi Help Center