Summary
Migrated/adapted from MoonshotAI/kimi-cli#2293 because Kimi CLI is evolving into Kimi Code CLI.
Kimi Code already has diagnostic/export work such as /export-debug-zip, but the user flow still appears to require a manual handoff: export a local bundle, find the right support channel, attach it, and describe the failure.
A one-step report command would make support reports more consistent while keeping the upload explicit and user-controlled.
Proposed UX
kimi report # preview + confirm + submit diagnostic bundle
kimi report --dry-run # generate the bundle locally only
Expected behavior:
- Reuse the existing debug/export bundle where possible.
- Include structured metadata: Kimi Code version, install source, OS, shell, provider/model, last error class, and redacted account/project/key identifiers when available.
- Show a clear preview/summary before any upload.
- Ask for explicit confirmation before sending anything.
- Upload to an official Moonshot support endpoint and return a report/ticket ID.
- Fall back to the local bundle path plus support contact if upload fails.
Why it matters
Most users will not complete a two-step export-and-email flow after an error. A single consent-based command would preserve privacy while giving maintainers consistent reports that are easier to triage.
Related
Summary
Migrated/adapted from MoonshotAI/kimi-cli#2293 because Kimi CLI is evolving into Kimi Code CLI.
Kimi Code already has diagnostic/export work such as
/export-debug-zip, but the user flow still appears to require a manual handoff: export a local bundle, find the right support channel, attach it, and describe the failure.A one-step report command would make support reports more consistent while keeping the upload explicit and user-controlled.
Proposed UX
Expected behavior:
Why it matters
Most users will not complete a two-step export-and-email flow after an error. A single consent-based command would preserve privacy while giving maintainers consistent reports that are easier to triage.
Related