Why does Kimi Code need Git Bash on Windows?

Kimi Code uses Git Bash as its runtime shell. Install Git for Windows first; if it lives in a non-standard location, set KIMI_SHELL_PATH so the CLI can find it.

What is the difference between Auto mode and Yolo?

Auto mode auto-approves actions under Kimi's automatic permission policy. Yolo auto-approves every tool call including file writes and shell commands. The two are mutually exclusive.

Kimi Code

Moonshot's Kimi Code CLI in Open Free Max — plan, auto and yolo permission modes, Skills folders, and the Git Bash requirement on Windows.

Kimi Code runs as an interactive session driven by keystrokes, like every other CLI in Open Free Max. It has one platform prerequisite worth knowing before you start.

Windows prerequisite: Git Bash

Kimi Code uses Git Bash as its runtime shell. Install Git for Windows first. If Git is installed somewhere unusual, set KIMI_SHELL_PATH to point at the shell — you can do it in the Environment variables field of Agent settings, which injects it into every Kimi session without touching your system environment.

What OFM does with it

Continue the last conversation. kimi --continue reopens the most recent session for the current folder. There is no resume-by-id.
No MCP injection. Kimi Code offers no launch-time channel that leaves your own configuration untouched, so MCP servers, the memory tool and the Obsidian vault are not wired in.
History is not ingested. Kimi transcripts are not part of the memory index.
Estimated accounting in the Consumption view.

Launch flags

Setting	Effect
Model	Model alias at launch. Empty = default (`kimi-for-coding`)
Plan mode	Starts in Plan mode — read-only exploration before changes
Auto mode	Automatic permission mode. Exclusive with Yolo
Yolo	Auto-approves every tool call, including file writes and shell. Trusted folders only
Skills folders	Loads Skills from these directories, one path per line
Additional arguments, Environment variables	Escape hatches

Skills

Kimi Code can load Skills — packaged instruction sets — from directories you list. Point the setting at a folder in the project to give every Kimi session in that project the same capabilities, without touching the CLI’s global configuration.

Installation

Install the Kimi Code CLI with the assistant in the agent tab. On Windows, install Git for Windows first, then re-check so the new command is found on your PATH.

Frequently asked

Why does Kimi Code need Git Bash on Windows?: Kimi Code uses Git Bash as its runtime shell. Install Git for Windows first; if it lives in a non-standard location, set KIMI_SHELL_PATH so the CLI can find it.
What is the difference between Auto mode and Yolo?: Auto mode auto-approves actions under Kimi's automatic permission policy. Yolo auto-approves every tool call including file writes and shell commands. The two are mutually exclusive.