MoonshotAI / MoonshotAI/kimi-code

feat: 增加 kimi doctor --json 本地诊断命令

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What feature would you like to see?

希望增加 kimi doctor 命令,并支持 kimi doctor --json 输出脱敏后的本地诊断报告,方便用户在提交 bug issue 前收集必要信息。

建议诊断内容包括:

  • Kimi Code 版本、安装来源、Node.js 版本、系统平台、架构、shell
  • KIMI_CODE_HOME、配置文件路径、日志路径、配置解析状态
  • 当前 provider / model 的解析结果
  • 登录状态,但不暴露 token 或 API key
  • MCP server 配置、连接状态、认证状态
  • 终端环境,例如 TERM、终端程序、tmux、WSL 等
  • 代理和网络相关环境变量,敏感信息需脱敏
  • session / log 基本清单,帮助排查问题
Additional information

Codex 已经有类似的 codex doctor --json,并且在 bug 模板中引导用户附上 doctor report。Kimi Code 目前已有日志和 kimi export,但缺少一个安全、只读、标准化的诊断入口。

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing logging and kimi export behavior, then compare the referenced codex doctor --json flow. Done means a read-only kimi doctor --json command produces a standardized local report covering the requested environment and status details while redacting tokens, keys, and other sensitive values.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cli, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.