Skip to content

docs(readme): add prerequisites list to Development section#2287

Open
ktwu01 wants to merge 1 commit into
MoonshotAI:mainfrom
ktwu01:docs/readme-dev-prerequisites
Open

docs(readme): add prerequisites list to Development section#2287
ktwu01 wants to merge 1 commit into
MoonshotAI:mainfrom
ktwu01:docs/readme-dev-prerequisites

Conversation

@ktwu01
Copy link
Copy Markdown

@ktwu01 ktwu01 commented May 14, 2026

Resolves #2274.

Change

Adds a ### Prerequisites subsection at the top of the README's ## Development section listing what a contributor needs installed before make prepare will work.

Why

Today the README jumps straight from the user-install instructions into make prepare with no statement of what the contributor needs first. New contributors hit one of:

  • make: command not found (Windows users without WSL or build tools)
  • uv: command not found (no link to install instructions in this section)
  • make build-web failing because Node.js / npm aren't installed
  • on Windows, the agent's Shell tool refuses to start because Git Bash isn't installed (src/kimi_cli/utils/environment.py's GitBashNotFoundError — easy to hit while testing your changes)
  • general confusion about whether they pip install something or rely on uv to manage the venv

What's listed

  • uv ≥ 0.8 (matches pyproject.toml's uv_build>=0.8.5,<0.10.0)
  • Python 3.14 (matches .python-version)
  • make (with WSL / MSYS2 / Chocolatey notes for Windows)
  • Node.js ≥ 20 + npm — flagged as only required for make build-web / make build
  • Git Bash on Windows — the surprising one; references the actual error class GitBashNotFoundError
  • Nix (optional) — points at the existing flake.nix as an all-in-one shortcut

All version pins verified against the actual repo files (.python-version, pyproject.toml, flake.nix, src/kimi_cli/utils/environment.py).

Diff

 ## Development

-To develop Kimi Code CLI, run:
+### Prerequisites
+
+- **uv** ≥ 0.8 — package + venv manager. Install: ...
+- **Python 3.14** — pinned by `.python-version`; uv will install it for you ...
+- **make** — runs the build/test targets in `Makefile`. ...
+- **Node.js ≥ 20 + npm** — only required if you'll run `make build-web` ...
+- **Git Bash (Windows only)** — kimi-cli's agent requires `bash.exe` ...
+- **Nix (optional)** — a `flake.nix` is provided; `nix develop` ...
+
+### Setup

 ```sh
 git clone https://github.com/MoonshotAI/kimi-cli.git

Pure docs change. No code touched.

🤖 Generated with Claude Code


Open in Devin Review

Lists uv (>=0.8 per pyproject.toml's uv_build constraint), Python
3.14 (per .python-version), make, Node.js (only for make build-web /
make build), Git Bash on Windows (required by the agent's Shell tool
per src/kimi_cli/utils/environment.py), and Nix as an optional
all-in-one shortcut via the existing flake.nix.

Surfaces the 'I just cloned and ran make prepare and got
make: command not found / uv: command not found / git-bash error'
class of contributor friction. No code changes.

Refs MoonshotAI#2274.
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7d90c03d48

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
- **uv** ≥ 0.8 — package + venv manager. Install: <https://docs.astral.sh/uv/getting-started/installation/> (`pyproject.toml` requires `uv_build>=0.8.5,<0.10.0`).
- **Python 3.14** — pinned by `.python-version`; uv will install it for you on first `uv sync` if missing. (`pyproject.toml` accepts `>=3.12`, but 3.14 matches the lockfile / CI environment.)
- **make** — runs the build/test targets in `Makefile`. Most Linux/macOS already have it; Windows users need WSL or a `make` from MSYS2 / Chocolatey.
- **Node.js ≥ 20 + npm** — only required if you'll run `make build-web` or `make build` (the latter embeds the web UI).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clarify Node.js is required for more than build targets

This prerequisite says Node.js/npm is only needed for make build-web or make build, but contributors following the same README are also told to run make format and make check, and both targets invoke npm via format-web and check-web in Makefile. In environments without Node.js, those common validation steps fail (npm not found), so this wording can mislead new contributors into an avoidable setup failure.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] README "Development" section is missing a prerequisite list

2 participants