3086e47039
Some checks are pending
CI / test-windows (push) Waiting to run
CI / lint (push) Waiting to run
CI / test (1) (push) Waiting to run
CI / test (2) (push) Waiting to run
CI / test (3) (push) Waiting to run
CI / test (4) (push) Waiting to run
CI / test (5) (push) Waiting to run
CI / test-pi-tui (push) Waiting to run
CI / build (push) Waiting to run
CI / typecheck (push) Waiting to run
Nix Build / Check flake.nix workspace sync (push) Waiting to run
Nix Build / nix build .#kimi-code (push) Blocked by required conditions
Release / Release (push) Waiting to run
Release / Deploy docs (push) Blocked by required conditions
Release / Native release artifact (push) Blocked by required conditions
Release / Publish native release assets (push) Blocked by required conditions
* fix(tui): correct YOLO and Auto permission mode descriptions * fix: unify YOLO and Auto permission mode descriptions across CLI, ACP, web, and docs * docs: correct YOLO and Auto mode descriptions in the interaction guide * fix: correct YOLO mode notices in session replay and vscode extension * feat(vscode): rename /afk command to /auto, keeping afk as hidden alias Also correct the stale 'afk' mode reference in the built-in MCP config skill guidance of both agent engines. * fix(vscode): forward engine approval requests instead of blanket-approving them The extension-level approval handler auto-approved every request when legacy yolo/afk was on, silently swallowing the sensitive-file, plan-review, and ask-rule prompts the engine yolo mode still sends. Forward every request to the user and let the engine permission mode do the auto-approving, matching TUI and web behavior. |
||
|---|---|---|
| .. | ||
| .vscode | ||
| docs | ||
| resources | ||
| scripts | ||
| shared | ||
| src | ||
| test | ||
| webview-ui | ||
| .vscode-test.mjs | ||
| .vscodeignore | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||
Kimi Code
AI coding assistant for VS Code, built for long-context workflows and complex coding tasks.
Features
- Works alongside you: Kimi autonomously explores your codebase, reads and writes code, and runs terminal commands with your permission
- Thinking controls: Toggle reasoning or choose a model-supported thinking effort
- Provider-aware models: Distinguish and select same-named models across configured providers
- Native editor integration: Review AI-proposed changes directly in VS Code's diff viewer
- MCP support: Extend capabilities with Model Context Protocol servers
- Slash commands: Quick actions like
/initto analyze your project and/compactto manage context
Install
Kimi Code requires VS Code 1.100.0 or later.
- Install from the VS Code Marketplace
- Open a folder in VS Code
- Click the Kimi icon in the Activity Bar
- Sign in with a kimi.com/code subscription, or use a provider already configured in the shared
config.toml
The extension runs the Kimi Code Node SDK in the VS Code Extension Host. When
the extension and the Kimi Code terminal app resolve to the same
KIMI_CODE_HOME, they share config.toml, MCP configuration, login state, and
sessions. The system-level KIMI_CODE_HOME environment variable is supported;
there is no separate VS Code setting for it. Do not run the same session from
both applications at the same time, because cross-process session locking is
not guaranteed.
After upgrading from version 0.5.x, the extension prompts before migrating any legacy data it finds. Migration copies or merges data into the current Kimi Code home and does not delete the legacy source. Legacy Kimi Code OAuth and MCP OAuth credentials are not copied, so those connections must be authorized again. See the changelog for the full compatibility notes.
Docs
Official doc for Kimi Code can be found at www.kimi.com/code/docs