docs: auto-sync with merged PRs (through 2026-07-29)

packages/kilo-docs/pages/ai-providers/moonshot.md

@@ -6,7 +6,7 @@ sidebar_label: Moonshot.ai
 
 # Using Moonshot.ai With Kilo Code
 
-Moonshot.ai is a Chinese AI company known for their **Kimi** models featuring ultra-long context windows (up to 200K tokens) and advanced reasoning capabilities. Their K2-Thinking model delivers extended thinking and problem-solving abilities.
+Moonshot.ai is a Chinese AI company known for their **Kimi** models featuring ultra-long context windows (up to 200K tokens) and advanced reasoning capabilities. Their latest Kimi K3 model delivers extended thinking and problem-solving abilities.
 
 **Website:** [https://www.moonshot.cn/](https://www.moonshot.cn/)
 
@@ -63,7 +63,7 @@ Then set your default model:
 ## Tips and Notes
 
 - **Ultra-Long Context:** Kimi models excel at handling large codebases and complex projects with their extended context windows.
-- **Reasoning Capabilities:** The K2-Thinking variant provides enhanced problem-solving through extended reasoning chains.
+- **Reasoning Capabilities:** Kimi K3 provides enhanced problem-solving through extended reasoning chains.
 - **Kimi-specific prompting:** Kilo automatically uses a Kimi-tuned system prompt for model IDs containing `kimi`; no extra configuration is required.
 - **Language Support:** Kimi models have strong support for both English and Chinese languages.
 - **Pricing:** Refer to the Moonshot.ai platform for current pricing information on different models.

packages/kilo-docs/pages/automate/agent-manager.md

@@ -11,7 +11,7 @@ The Agent Manager is a **full-panel editor tab** built directly into the extensi
 
 - Multiple parallel sessions, each in its own git worktree
 - A diff/review panel showing changes vs. the parent branch
-- Dedicated VS Code integrated terminals per session
+- Dedicated terminals per session, in the VS Code integrated terminal or an embedded side panel
 - Setup scripts and `.env` auto-copy on worktree creation
 - Session import from existing branches, external worktrees, or GitHub PR URLs
 - "Continue in Worktree" to promote a sidebar session to the Agent Manager
@@ -122,6 +122,8 @@ You can run up to 4 parallel implementations of the same prompt across separate
 2. Optionally assign different models to each version
 3. Kilo creates one worktree + session per version and runs them in parallel
 
+With **Compare Models**, checked models that support reasoning variants get a **Reasoning effort** dropdown next to the version count, so compared worktrees can run the same prompt at different effort levels. The collapsed selector shows the picked effort next to the model name (e.g. "Claude Opus 4.8 (high)"). Leaving the dropdown on **Default** — or using a model without variants — runs that version at the model's default effort.
+
 ### Importing Existing Work
 
 - **From a branch:** Import an existing git branch as a worktree
@@ -136,6 +138,7 @@ Imported work stays associated with its branch or worktree and can be continued
 - Create a worktree session to start a new agent in an isolated branch
 - Press `Cmd+T` (macOS) / `Ctrl+T` (Windows/Linux) to start another session in the selected worktree
 - Use session history to reopen local sessions or preview cloud sessions
+- When a managed worktree is selected, session history gains a **Worktree** tab listing only sessions assigned to that worktree; **Local** remains the aggregate history across the workspace and every managed worktree
 - Continue a cloud session locally from Agent Manager using the same extension sign-in and provider settings
 
 ### Renaming Worktrees
@@ -159,7 +162,9 @@ Each request can include 1-20 tasks. Each task must include at least one of `pro
 
 The companion `agent_manager_models` tool searches models and their supported reasoning variants on demand. Results are grouped by model name (with the offering providers listed for reference) and limited to 20 per call, so the full catalog is never added to the conversation context.
 
-The tool uses the `agent_manager` permission. Approval prompts are scoped to the requested capability, so approving `worktree` does not automatically approve `local`, an overview, or a targeted prompt. Prompting an existing managed session requires an explicit `prompt` approval the first time, even if Agent Manager session creation was previously approved broadly.
+The same tool also manages existing sessions. It can return a compact overview of sections, worktrees, and local sessions, send a prompt to one managed session, or stop a managed session. Stopping aborts the session's active work and removes it from the panel, just like closing the session tab.
+
+The tool uses the `agent_manager` permission. Approval prompts are scoped to the requested capability, so approving `worktree` does not automatically approve `local`, an overview, or a targeted prompt. Prompting an existing managed session requires an explicit `prompt` approval the first time, even if Agent Manager session creation was previously approved broadly. Stopping a session likewise requires an explicit `stop` approval.
 
 ## Sections
 
@@ -219,11 +224,30 @@ See [Agent Manager Workflows](/docs/automate/agent-manager-workflows#merging-wor
 
 ## Terminals
 
-Each session has a dedicated integrated terminal rooted in the session's worktree directory. Press `Cmd+/` (macOS) / `Ctrl+/` (Windows/Linux) to focus the terminal for the active session.
+Each session has a dedicated terminal rooted in the session's worktree directory. Press `Cmd+/` (macOS) / `Ctrl+/` (Windows/Linux) to open or focus the terminal for the active session.
+
+The terminal button in the toolbar is a split button: click it to open a terminal in the current destination, or open its dropdown to choose where terminals open:
+
+- **VS Code terminal** (default) — opens or focuses the VS Code integrated terminal.
+- **Agent Manager panel** — opens an embedded terminal in the right-hand side panel, next to the chat.
+
+The choice is saved in the `kilo-code.new.agentManager.terminalButtonDestination` setting and applies to both the button and the `Cmd+/` / `Ctrl+/` shortcut.
+
+### Side Panel Terminals
+
+With the **Agent Manager panel** destination, terminals open in the side panel that also hosts the diff view. You can switch between the diff and the terminal freely, and resize the panel with its drag handle — the panel remembers one width per mode.
+
+The panel supports multiple terminals per context (local, or per worktree):
+
+- The header is a tab strip: click a tab to switch, click **+** to open another terminal, and click **×** (or middle-click) to close a single terminal. Drag tabs to reorder them.
+- New terminals are named with the lowest free "Terminal N" number, and tabs pick up the live title from the shell or running program, so a dev server or editor names its own tab.
+- `Cmd+W` (macOS) / `Ctrl+W` (Windows/Linux) with a side terminal focused closes that terminal. Closing the last terminal leaves the panel on its empty state.
+
+Hiding the panel keeps its terminals running in the background — scrollback and running processes survive, and the same terminals are there when you reopen the panel or switch worktrees. When the panel hides while the terminal held focus, focus returns to the chat input. Side panel terminals are not kept across webview reloads.
 
 ### Switching Between Terminal and Agent Manager
 
-A common workflow is letting the agent work, then switching to the terminal to run tests or inspect the worktree, then switching back to control the agent:
+With the default **VS Code terminal** destination, a common workflow is letting the agent work, then switching to the terminal to run tests or inspect the worktree, then switching back to control the agent:
 
 1. **Agent Manager → Terminal:** Press `Cmd+/` (macOS) / `Ctrl+/` (Windows/Linux) to open and focus the terminal for the current session. The terminal runs inside the session's worktree, so commands like `npm test` or `git status` operate on the agent's isolated branch.
 2. **Terminal → Agent Manager:** Press `Cmd+Shift+M` (macOS) / `Ctrl+Shift+M` (Windows/Linux) to bring focus back to the Agent Manager panel and its prompt input. This works from anywhere in VS Code — the terminal, another editor tab, or the sidebar.
@@ -362,7 +386,7 @@ Closing a managed worktree removes it from Agent Manager, deletes its `.kilo/wor
 | `Cmd+W` | `Ctrl+W` | Close current tab |
 | `Cmd+Alt+Up` / `Down` | `Ctrl+Alt+Up` / `Down` | Previous / next worktree |
 | `Cmd+Alt+Left` / `Right` | `Ctrl+Alt+Left` / `Right` | Previous / next tab in worktree |
-| `Cmd+/` | `Ctrl+/` | Focus terminal for current session |
+| `Cmd+/` | `Ctrl+/` | Open / focus terminal for current session (destination set by the terminal button dropdown) |
 | `Cmd+D` | `Ctrl+D` | Toggle diff panel |
 | `Cmd+E` | `Ctrl+E` | Run / stop run script |
 | `Cmd+Shift+/` | `Ctrl+Shift+/` | Show keyboard shortcuts |

packages/kilo-docs/pages/automate/code-reviews/github.md

@@ -54,8 +54,11 @@ Once configured, the Review Agent automatically runs when:
 | PR reopened | ✅ Yes |
 | Draft PR marked ready | ✅ Yes |
 | Draft PR opened | ❌ Skipped |
+| PR opened by a bot | ❌ Skipped by default |
 | PR closed | ❌ No |
 
+Bot-authored PRs (Dependabot, Renovate, and other automation accounts) are detected with GitHub's author metadata and skipped before any review is created. To have them reviewed, turn off **Skip pull requests from bots** under Global Settings in the Code Reviews configuration. Reviews you start manually are not affected by this setting.
+
 ## What to Expect
 
 When a review triggers:

packages/kilo-docs/pages/automate/code-reviews/overview.md

@@ -66,6 +66,10 @@ To use it:
 
 Kilo reads `REVIEW.md` from the PR/MR base branch, not the feature branch. That prevents an unreviewed change from rewriting the review policy used to evaluate itself. If the file is disabled, missing, empty, or unreadable, Kilo falls back to built-in guidance. If it is longer than 10,000 characters, Kilo truncates it and notes that in the review summary footer.
 
+{% callout type="note" title="Custom Instructions is being deprecated" %}
+The **Custom Instructions** field in Code Reviews settings is planned for deprecation in favor of `REVIEW.md`. The field no longer appears for configurations that have never used it. Configurations that already have a value keep the field, and stored instructions still apply to reviews — but you should move those guidelines into a `REVIEW.md` file in your repository.
+{% /callout %}
+
 ### Default Sub-Agent Usage
 
 By default, Code Reviews uses sub-agents only when they materially improve coverage. After reading the diff, the reviewer estimates changed file count and changed lines, then chooses the largest tier triggered by either signal.
@@ -113,6 +117,39 @@ Each sub-agent must stay read-only, must not post comments, and must return find
 
 `REVIEW.md` can change review policy and sub-agent usage, but it cannot override Kilo's hard safety constraints, read-only mode, non-interactive execution, platform API instructions, diff-line rules, duplicate-comment rules, or output formatting requirements.
 
+## Council Reviews
+
+A council review runs several specialist models over the same change and combines their results into a single decision. When you create a review job, you can enable a council, select the specialist models, and pick a governance mode.
+
+Each specialist reports findings with a severity — `critical`, `warning`, `suggestion`, or `nitpick` — and the outcome is computed deterministically from those findings in code, not voted on by the models:
+
+- A specialist **blocks** when it reports at least one `critical` finding; otherwise it **passes**. `critical` is the only blocking severity.
+- A specialist with no usable result is shown as **No result** rather than counted as a pass or block.
+- When the review completes, Kilo posts a **Council Review** section on the PR/MR with the decision, the governance mode, and a per-specialist table (specialist, model, highest severity, finding count). Re-running the review updates this section in place.
+
+### Governance Modes
+
+| Mode | Behavior |
+|---|---|
+| **Advisory** (default) | Reports each specialist's vote with no aggregate decision and never blocks merging. |
+| **Unanimous** | Blocks unless every specialist passes. |
+| **Majority** | Blocks when block votes outnumber pass votes. |
+
+Under Unanimous or Majority, a `block` decision fails the PR/MR status check, so the change cannot be merged. If specialist results are missing or invalid, these modes fail closed to `block`. Reviews you start manually report the decision but never block merging.
+
+### Per-Repository Council Opt-In
+
+Automated (webhook-triggered) reviews run as standard reviews by default. To run a council review automatically when a repository's pull requests are opened or updated, opt the repository in:
+
+1. Open the Review Agent configuration and turn on **Advanced Settings**.
+2. In the per-repository overrides, enable **Council** for each repository that should receive automated council reviews.
+
+Opted-in repositories run the shared council configuration — the same specialist models and governance mode — on automated reviews, and the council decision drives the PR/MR status check. All other repositories continue to receive standard reviews, and a repository falls back to a standard review whenever the council configuration is missing or inactive.
+
+### Automated Review Exclusions
+
+On GitHub, automated (webhook-triggered) reviews never use a council for draft PRs, bot-authored PRs, or PRs opened from a fork — these run as standard reviews instead, even when the repository is opted in to council reviews. These exclusions are built in and cannot be overridden by configuration. The review still runs; only the council review type is skipped. Reviews you start manually can always use a council.
+
 ## Local Code Reviews
 
 Code Reviewer is also available locally. This is valuable for developers who want to review their code before pushing a pull request to their team publicly, or for developers who want reviews and don't need to ship a pull request to GitHub.
@@ -160,7 +197,7 @@ When a pull request or merge request is opened or updated:
 Reviews are posted directly in your platform (GitHub or GitLab) as if coming from a team reviewer.
 
 {% callout type="info" title="Bot-generated PRs are ignored by default" %}
-Kilo does not automatically review pull or merge requests opened by bots, such as Dependabot, Renovate, or other automation accounts. This keeps review credits and notifications focused on human-authored changes.
+Kilo does not automatically review pull requests opened by bots, such as Dependabot, Renovate, or other automation accounts. This keeps review credits and notifications focused on human-authored changes. On GitHub, the **Skip pull requests from bots** toggle in Global Settings controls this behavior and is on by default — turn it off to have bot-authored PRs reviewed. Reviews you start manually are unaffected either way. Bot detection relies on GitHub's author metadata, so the toggle does not appear for GitLab.
 {% /callout %}
 
 ## Review Styles

packages/kilo-docs/pages/automate/tools/index.md

@@ -21,7 +21,7 @@ Tools are organized into logical groups based on their functionality:
 | **Web Group** | Fetch and search web content | `webfetch`, `websearch` | Research, documentation lookup |
 | **Browser Group** | Web browser automation | `kilo-playwright_*` (via built-in Playwright MCP) | Browser testing and interaction |
 | **MCP Group** | External tool integration | MCP server tools (namespaced as `{server}_{tool}`) | Specialized functionality via MCP |
-| **Workflow Group** | Sub-agents and task management | `question`, `task`, `todowrite`, `todoread`, `plan`, `skill`, `agent_manager` | Context switching and task organization |
+| **Workflow Group** | Sub-agents and task management | `question`, `task`, `todowrite`, `todoread`, `plan`, `skill`, `agent_manager`, `notify_user` | Context switching and task organization |
 
 ### Always Available Tools
 
@@ -64,6 +64,18 @@ These tools help Kilo Code access web content:
 - `webfetch` - Fetches a URL and returns the content
 - `websearch` - Searches the web (available to Kilo/OpenRouter users)
 
+#### Web Search Providers
+
+The `websearch` tool routes searches through one of two providers, Exa or Parallel, chosen per session. Set the `KILO_WEBSEARCH_PROVIDER` environment variable to `exa`, `parallel`, or `kilo-exa` to force a provider.
+
+When the provider is Exa, authentication decides how the search is transported:
+
+1. If `EXA_API_KEY` is set, the search uses your own Exa API key (BYOK).
+2. Otherwise, if you are signed in to Kilo, the search routes through the Kilo proxy and is billed to your Kilo account — no Exa key needed. Set `KILO_WEBSEARCH_PROVIDER=kilo-exa` to force this path (requires Kilo sign-in).
+3. If neither is available, the search falls back to Exa's unauthenticated endpoint.
+
+The `numResults` parameter defaults to 8 and is capped at 10.
+
 ### Browser Tools
 
 The VS Code extension has a built-in browser automation tool powered by [Playwright MCP](https://www.npmjs.com/package/@playwright/mcp). Enable it in Settings → Browser Automation. When enabled, it registers an MCP server named `kilo-playwright` and exposes tools such as:
@@ -91,6 +103,7 @@ These tools help manage the conversation and task flow:
 - `plan` - Enters structured planning mode
 - `skill` - Invokes a reusable skill (Markdown instruction module)
 - `agent_manager` - Starts Agent Manager local or worktree sessions in VS Code
+- `notify_user` - Sends a push notification to your phone via the Kilo mobile app (requires a session connected to Kilo cloud)
 
 ## Tool Calling Mechanism