docs(kilo-docs): consolidate older docs-sync rollovers

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

@@ -169,6 +169,7 @@ Layer review in before asking a teammate:
 - **`/review`** — slash command, AI review of staged, unstaged, and untracked changes in the worktree when run without arguments. Good as a last pass before committing.
 - **`/review uncommitted [guidance]`** — explicitly review uncommitted changes, optionally focusing the review with guidance.
 - **`/review branch [base] [guidance]`** — review the whole branch vs. its detected or specified base, with optional guidance.
+- **`/review worktree [guidance]`** - review committed, staged, unstaged, and untracked changes against the worktree's recorded parent branch. Available only in Agent Manager managed worktree sessions.
 - **`/review <commit-hash>` or `/review <PR URL or number>`** — review a specific commit or pull request.
 - **`kilo review` in CI** — automated PR review. See [Code Reviews](/docs/automate/code-reviews/overview) for the setup.
 - **Human review** — push the branch from the session terminal and `gh pr create`. The PR badge appears on the worktree and stays in sync with CI and reviews. Review, comment on, and merge the pull request from the internal PR panel; see [Reviewing a pull request](/docs/automate/agent-manager#reviewing-a-pull-request).
@@ -198,11 +199,7 @@ Three ways, pick based on how much collaboration the change needs:
 
 ### Parent branch → worktree
 
-When the parent branch moves ahead, ask the agent from the worktree's session:
-
-> Merge the latest `origin/main` into this branch and resolve any conflicts. Do not use `git stash`.
-
-Save this as a reusable slash command if you do it often.
+When the parent branch moves ahead, run `/update-from-base` in the managed worktree's chat. It asks the agent to fetch and merge the saved base, preserving uncommitted edits without Git stash. The [Push Pull Request Fixes](/docs/automate/agent-manager#push-pull-request-fixes) setting controls whether it is also asked to push after checks pass. See [Update from the base branch](/docs/automate/agent-manager#update-from-the-base-branch) for details.
 
 {% callout type="danger" %}
 **Never use `git stash` inside a worktree.** Stashes live in the shared `.git` directory that every worktree points at, so a stash made in one worktree can be popped in another — crossing uncommitted changes between agents. Use a WIP commit or a temporary branch instead.
@@ -216,7 +213,7 @@ The Agent Manager is good at conflict resolution when you give it context. A low
 
 ### When several worktrees finish at once
 
-Merge the most foundational one first. Then, in each remaining worktree, ask the agent to pull the updated parent branch in (same prompt as above) before merging. The agent handles the merge direction and only escalates conflicts it cannot resolve.
+Merge the most foundational one first. Then run `/update-from-base` in each remaining worktree before merging it. Give the agent context when a conflict needs a decision about the intended behavior.
 
 ## Hygiene
 

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

@@ -79,14 +79,19 @@ When a review triggers:
 
 The repository list is synced from GitHub and can be refreshed from the configuration page.
 
+### Per-repository overrides
+
+Turn automated reviews on or off for an individual repository to override the installation default. For example, disable a noisy repository or enable one repository while the default is off. Repositories with reviews disabled do not start automated reviews for incoming pull requests.
+
 ## Troubleshooting
 
 ### Reviews are not triggering
 
 1. Verify the GitHub App is installed and has access to the repository
-2. Check that the Review Agent is **enabled** in the Code Reviews configuration
+2. Check that reviews are enabled by the installation default or a per-repository override
 3. Ensure the repository is in the allowed list (if using "Selected repositories" mode)
-4. Confirm the PR is not a draft
+4. Check that a per-repository override has not disabled reviews
+5. Confirm the PR is not a draft
 
 ### Reviews are failing
 

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

@@ -124,6 +124,7 @@ Use `/review` for all local code reviews:
 - **`/review`** — Review uncommitted changes (staged, unstaged, and untracked) when run without arguments
 - **`/review uncommitted [guidance]`** — Review uncommitted changes with optional guidance
 - **`/review branch [base] [guidance]`** — Review your current branch vs. its detected or specified base, with optional guidance
+- **`/review worktree [guidance]`** - In an Agent Manager worktree session, review committed, staged, unstaged, and untracked changes against the recorded parent branch
 - **`/review <commit-hash>`** — Review a specific commit
 - **`/review <PR URL or number>`** — Review a pull request
 

packages/kilo-docs/pages/automate/integrations.md

@@ -30,7 +30,7 @@ Before connecting:
 - For GitHub: You need permission to install GitHub Apps for the repositories you want Kilo to access.
 - For GitLab: You need **Maintainer** role (or higher) on the projects you want to connect.
 - For DoltHub: You need a DoltHub account to authorize the OAuth connection.
-- (Optional) If you're connecting an organization, you must be an admin or have app installation permissions.
+- For a Kilo organization, adding a GitHub integration requires the **Owner** or **Admin** role, in addition to permission to install the app on GitHub.
 
 ---
 
@@ -161,16 +161,18 @@ Once your integrations are connected, the following features are enabled in Kilo
 - Use DoltHub alongside GitHub or GitLab when a workflow also needs repository access
 - Authorize Gas Town Wasteland to fork commons databases, push claims and evidence, and manage DoltHub PRs. Wasteland also supports an advanced API token option when OAuth is not available.
 
-### Upcoming:
+### Bitbucket
 
-- **Bitbucket Integration**
+Organization accounts can connect Bitbucket Cloud and select its repositories when starting [Cloud Agent sessions](/docs/code-with-ai/platforms/cloud-agent) on the web or in the mobile app. Connect Bitbucket from your organization's **Integrations** page. Bitbucket is not available for personal accounts.
 
 ---
 
 ## Managing or Removing the Integration
 
 ### GitHub
 
+An organization Owner or Admin can connect multiple GitHub organizations. Click **Add organization** and repeat the installation flow. Each installation has its own connection status, repository scope, selected repository list, and management actions. Personal accounts use a single GitHub connection.
+
 From the **Integrations** page, click "Manage on GitHub" to:
 
 - View the GitHub account you connected

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

@@ -19,7 +19,7 @@ Tools are organized into logical groups based on their functionality:
 | **Edit Group** | File system modifications | `edit`, `write`, `apply_patch` | Code changes and file manipulation |
 | **Execute Group** | Shell command execution | `bash` | Running scripts, building projects |
 | **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 |
+| **Browser Preview** | Agent Manager's built-in browser preview | `browser_open` | Previewing and checking locally running apps |
 | **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`, `board_post`, `board_read` | Context switching and task organization |
 
@@ -94,15 +94,11 @@ Set the `KILO_WEBSEARCH_PROVIDER` environment variable to force a provider:
 
 ### 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:
+The VS Code extension's experimental `browser_open` tool opens a local application in Agent Manager's Browser panel and returns a screenshot and diagnostics. Enable **Browser Automation** under **Settings > Experimental**. It requires installed Chrome or compatible Playwright Chromium.
 
-- `kilo-playwright_browser_navigate` - Navigate to a URL
-- `kilo-playwright_browser_click` - Click an element
-- `kilo-playwright_browser_type` - Type text into an element
-- `kilo-playwright_browser_screenshot` - Capture a screenshot
-- `kilo-playwright_browser_snapshot` - Capture an accessibility snapshot
+The `browser_open` automation browser accepts HTTP URLs on `localhost` or `127.0.0.1` only, and blocks resources from other origins. See [Browser previews](/docs/automate/agent-manager#browser-previews) for setup and element feedback.
 
-These follow the same permission model as all MCP tools (see below).
+This restriction is specific to `browser_open`, not Kilo's web access in general. Use `websearch` and `webfetch` to find and read public web pages. Browser tools from a separately configured MCP server can provide interactive web browsing according to that server's capabilities and permissions.
 
 ### MCP Tools
 
@@ -118,6 +114,7 @@ These tools help manage the conversation and task flow:
 - `todoread` - Reads the current session TODO list
 - `plan` - Enters structured planning mode
 - `skill` - Invokes a reusable skill (Markdown instruction module)
+- `open_plan` - Opens a saved plan for review in the VS Code extension
 - `agent_manager` - Starts Agent Manager local or worktree sessions in VS Code
 - `board_post` / `board_read` - Exchange messages on the experimental Kilo Swarm board
 

packages/kilo-docs/pages/code-with-ai/agents/context-mentions.md

@@ -26,6 +26,8 @@ Type `@` in the chat input to get autocomplete suggestions. You can mention:
 | **Terminal** | In the sidebar, include the active VS Code terminal output. In Agent Manager, include the focused terminal for the selected session or worktree, including embedded **Run** and **Setup** tabs. | `@terminal` |
 | **Git Changes** | Attach uncommitted working-tree diffs and new files | `@git-changes` |
 | **Past chats** | Add a previous session's chat history as context | `@` → **Past chats** → pick a session |
+| **Worktrees** | In Agent Manager, reference another worktree's location and session metadata | `@` → **Worktrees** → pick a worktree |
+| **Model** | Reference a model for a subagent or Agent Manager session | `@` → **Model** → pick a model |
 
 Selecting a suggestion inserts the mention and highlights it in the input. File contents, terminal output, and git changes are attached as context when you send the message.
 
@@ -37,6 +39,12 @@ Choosing **Past chats** from the `@` menu opens a searchable picker of sessions
 
 Very long chat histories are truncated, keeping the beginning and end, so a single mention cannot fill the context window.
 
+### Referencing worktrees and models
+
+In Agent Manager, choose **Worktrees** to search other worktrees by name, branch, or session title. A worktree mention includes its path, branch, base branch, and session metadata. It does not attach files, diffs, or chat history, and does not change your working directory.
+
+Choose **Model** to insert an inline `@provider/model` reference. Use it to request a particular model for a subagent or Agent Manager session. It does not attach a file or change the current session's model. Subagent overrides require [Task Subagent Model Selection](/docs/getting-started/settings#task-subagent-model-selection).
+
 ### Drag and Drop
 
 You can also add file mentions by dragging and dropping:

packages/kilo-docs/pages/code-with-ai/agents/model-selection.md

@@ -11,10 +11,10 @@ Instead of maintaining a static list that's perpetually behind, we built somethi
 
 ## Model Routing and Configuration
 
-Kilo's IDE Extension and CLI configurations have four separate, independently configurable model slots:
+You can configure models separately for different tasks in the VS Code extension and kilo CLI:
 
 - **Main model** — the primary model your agent uses for coding tasks, chat, and reasoning. This is what you pick with the model selector, `/models`, or the `model` key in `kilo.jsonc`. See [How to Select and Switch Models](#how-to-select-and-switch-models) for the full precedence order and per-agent config.
-  - The main model is also used for context compaction/summarization and todo-list generation.
+  - The main model is also used for todo-list generation, and for context compaction when no compaction model is set.
 - **Small model** — a lightweight model used for session title generation, commit message generation, and prompt enhancement. Configured with the `small_model` key in `kilo.jsonc`, or the **Small Model** field on the **Settings → Models** tab.
   - If left unset, Kilo resolves it according to the following logic: 
     1. Find a small/cheap variant on your current provider (e.g. Haiku on Anthropic, Flash on Gemini).
@@ -23,6 +23,7 @@ Kilo's IDE Extension and CLI configurations have four separate, independently co
 - **Subagent model** — the default model for subagents launched by the `task` tool. Configured with the `subagent_model` key in `kilo.jsonc`, or the **Subagent Model** field on the **Settings → Models** tab.
   - If left unset, inherits whichever model the parent agent session is currently using.
 - **Autocomplete model** — the model used for inline code completions as you type. See [Autocomplete: Provider and Model](/docs/code-with-ai/features/autocomplete#provider-and-model) for how to configure it.
+- **Compaction model** - the model used to summarize context. Set `agent.compaction.model` in `kilo.jsonc`, or choose **Compaction model** under **Settings → Models**. If unset, compaction uses the current session's model. See [Context Condensing](/docs/customize/context/context-condensing#use-a-different-model-for-compaction).
 
 ### Configuring Local Usage
 
@@ -153,6 +154,12 @@ The Settings UI writes the same `agent.<name>.model` entry, so either method pro
 
 For details on configuring subagent models, see [Custom Subagents](/docs/customize/custom-subagents).
 
+### Per-task model selection (experimental)
+
+Enable [Task Subagent Model Selection](/docs/getting-started/settings#task-subagent-model-selection) to request a different model, provider, or reasoning effort for an individual subagent task. It is off by default. Overrides require your explicit request; the agent does not choose a different model on its own based on task complexity, cost, or latency.
+
+Invalid selections fail instead of silently falling back. Resumed tasks keep their last model and reasoning effort unless you request an override.
+
 ## Selecting a Model or Agent via a Link (VS Code)
 
 The VS Code extension supports a `vscode://` protocol handler that lets you open VS Code and automatically select a model, an agent, or both — no manual picker interaction required. This is useful for sharing model recommendations, launching a specific model tier from a web page, or switching quickly to a preferred agent.

packages/kilo-docs/pages/code-with-ai/agents/orchestrator-mode.md

@@ -25,7 +25,9 @@ Now, **subagent support is built into agents that have full tool access** (Code,
 
 1. The agent analyzes a complex task and decides a subtask would benefit from isolation.
 2. It launches a subagent session using the `task` tool (e.g., `general` for autonomous work, `explore` for codebase research).
-3. The subagent runs in its own isolated context — separate conversation history, no shared state.
-4. When done, the subagent returns a summary to the parent agent, which continues its work.
+3. The subagent has a separate conversation history but shares the parent's project directory or worktree. It does not isolate file edits.
+4. A foreground task returns its result before the parent continues. A background task lets the parent continue immediately and delivers its result later.
 
 Agents can launch multiple subagent sessions concurrently for parallel work.
+
+[Kilo Swarm](/docs/getting-started/settings#kilo-swarm) lets a main session and its task descendants exchange findings on a shared board. It works with your current agent and does not require the deprecated Orchestrator mode. Swarm is on by default; turn it off in **Settings > Agent Behaviour** or set `experimental.shared_agent_board` to `false` in `kilo.jsonc`. For separate branches and checkouts, use [Agent Manager worktree sessions](/docs/automate/agent-manager#orchestration-model) instead.

packages/kilo-docs/pages/code-with-ai/agents/using-agents.md

@@ -68,7 +68,7 @@ There are several ways to switch agents:
 | **Description** | An experienced technical leader and planner who helps design systems and create implementation plans |
 | **Tool Access** | Read-only tools plus restricted file editing (plan files in `.kilo/plans/` only) |
 | **Ideal For** | System design, high-level planning, and architecture discussions |
-| **Special Features** | Similar to the legacy extension's "Architect" mode, with a planning-focused approach |
+| **Special Features** | Similar to the legacy extension's "Architect" mode, with a planning-focused approach. In VS Code, the saved plan opens in the editor when ready for review. |
 
 ### debug