From 88be21a97367987bb1a1da9f18658ef46b9a8c64 Mon Sep 17 00:00:00 2001 From: Mark IJbema Date: Thu, 2 Apr 2026 14:19:05 +0200 Subject: [PATCH] docs: update code review FAQ to reference /local-review commands --- .../platforms/vscode/whats-new.md | 25 +------------------ 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/whats-new.md b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/whats-new.md index 9733134fbce..d7d82cfcc85 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/whats-new.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/whats-new.md @@ -27,42 +27,19 @@ Checkpoints are now called **snapshots** in the new extension. They use git-base The old auto-confirm commands UI has been replaced by a granular per-tool permission system. Open **Settings → Auto Approve** to configure each tool (bash, read, edit, glob, grep, etc.) with **Allow**, **Ask**, or **Deny**. There is no longer a separate command allowlist — shell execution is controlled by the `bash` tool permission. See [Auto-Approving Actions](/docs/getting-started/settings/auto-approving-actions) for more information. -### Where did the file reading settings go? - -File reading is now controlled by the `read` tool permission in **Settings → Auto Approve**. By default, file reading is allowed, but `.env` files will prompt for approval. You can adjust this behavior per tool in the Auto Approve tab. - -### Where is the UI for configuring local LLM providers? - -Local LLM providers like Ollama and LM Studio can be configured through **Settings → Providers**. The extension and CLI share the same config, so changes in either place are reflected in both. See the [Local Models](/docs/automate/extending/local-models) documentation for setup instructions. - -### The model selection feels bloated. Can I simplify it? - -Model selection has been streamlined in the new extension. You can configure your preferred models to reduce clutter. See [Model Selection](/docs/code-with-ai/agents/model-selection) for details on how to customize which models appear in the selector. - ### Is the context progress graph still available? The context progress graph is being evaluated for the new extension. This feature may be reintroduced in a future update. -### Where are the copy buttons in chat? - -Copy functionality is available in the chat interface. Hover over a message or code block to reveal the copy button. - -### Where did the in-chat UI for skills, commands, and MCPs go? - -MCP configuration has been migrated to the new settings panel. If you had MCPs configured in the old extension, they are automatically migrated to the new version. You can manage MCP servers, skills, and commands through the settings panel. See [MCP Overview](/docs/automate/mcp/overview) for more information. - ### Where is the diff view for file changes? Each message that caused file changes shows a **diff badge** in the chat — click it to open the Diff Viewer and review what changed. The Agent Manager also includes a built-in diff reviewer that shows every change file by file, in unified or split view. ### How do I do code reviews in the new extension? -The Agent Manager includes inline code review — you can leave **line-level review comments directly on the diff**, the same way you would on a pull request. Click a line, type your feedback, and hit "Send all to chat" to send every comment with its file path and line number as structured context to the agent. See the [Agent Manager](/docs/automate/agent-manager) documentation for details. +You can now trigger local AI-powered code reviews directly from the CLI using two commands: **`/local-review`** to review all changes on your current branch vs the base branch, and **`/local-review-uncommitted`** to review staged and unstaged changes. In VS Code, select "Review" from the mode dropdown and click "Send". See the [Code Reviews](/docs/automate/code-reviews/overview) documentation for the full setup and options. ### Where did orchestrator mode go? Orchestrator mode is deprecated. Agents with full tool access (Code, Plan, Debug) can now **delegate to subagents automatically** — you no longer need a dedicated orchestrator. Just pick the agent for your task and it will coordinate subagents when helpful. You can also define your own [custom subagents](/docs/customize/custom-subagents). See the [Orchestrator Mode](/docs/code-with-ai/agents/orchestrator-mode) page for the full details on what changed. -### I had custom command allowlists — where did they go? - -The new extension no longer uses a command allowlist. Instead, shell execution is controlled by the `bash` tool permission in **Settings → Auto Approve**. You can set it to Allow, Ask, or Deny. When set to Ask, you approve or deny each individual command invocation at runtime.