docs: auto-sync with merged PRs (through 2026-08-22)

packages/kilo-docs/lib/nav/collaborate.ts

@@ -8,6 +8,10 @@ export const CollaborateNav: NavSection[] = [
       { href: "/collaborate/sessions-sharing", children: "Sessions & Sharing" },
     ],
   },
+  {
+    title: "Account",
+    links: [{ href: "/collaborate/data-exports", children: "Data Exports" }],
+  },
   {
     title: "Kilo for Teams",
     links: [

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

@@ -65,3 +65,4 @@ Then set your default model:
 - **Performance:** MiniMax M2.1 emphasizes fast inference, strong coding ability, and exceptional tool-calling performance.
 - **Context Window:** MiniMax models support ultra-long context windows suitable for large codebases and agent workflows.
 - **Pricing:** Pricing varies by model, with input costs ranging from $0.20 to $0.30 per million tokens and output costs from $1.10 to $2.20 per million tokens. Refer to the MiniMax documentation for the most current pricing information.
+- **Token Plan usage:** If you configure a MiniMax coding plan (Token Plan) key, its remaining quota appears under **Plans & usage** in the VS Code profile view and via `/usage` in the CLI.

packages/kilo-docs/pages/ai-providers/openai-compatible.md

@@ -39,12 +39,12 @@ Use Kilo Code's native `azure` provider instead. If your Azure deployment name d
 - **Provider API** — Select **OpenAI Compatible** for an OpenAI Chat Completions-compatible endpoint. Use **OpenAI Responses** for OpenAI and xAI models. Use **Anthropic Messages** for Anthropic and MiniMax models.
 - **Base URL** — The provider's API endpoint (e.g., `https://api.your-provider.com/v1`). Kilo auto-fetches available models when a valid URL exposes an OpenAI-compatible models endpoint. For Azure OpenAI GPT-5, use the native `azure` provider instead.
 - **API key** — Your API key. Optional — leave empty if authentication is handled via headers.
-- **Models** — Add models manually or select from the auto-fetched list (see [Automatic Model Detection](#automatic-model-detection) below).
+- **Models** — Add models manually or select from the auto-fetched list (see [Automatic Model Detection](#automatic-model-detection) below). Each model has **Reasoning** and **Image** checkboxes, with **Toggle reasoning for all** and **Toggle image for all** buttons to flip every model at once.
 - **Headers** (optional) — Custom HTTP headers as key-value pairs.
 
 4. Click **Submit** to save. The provider's models appear in the model picker.
 
-For additional model configuration (token limits, tool calling, variants), edit the `kilo.jsonc` config file directly — see the **CLI** tab or the [Custom Models](/docs/code-with-ai/agents/custom-models) guide.
+For additional model configuration (token limits, tool calling, variants), edit the `kilo.jsonc` config file directly — when editing a saved provider, click **Edit advanced settings in the JSON config file** to jump straight to its config entry. See the **CLI** tab or the [Custom Models](/docs/code-with-ai/agents/custom-models) guide.
 
 ### Automatic Model Detection
 

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

@@ -104,6 +104,37 @@ Hovering over a worktree item shows a card with additional PR details:
 
 PR badges update automatically in the background. The active worktree refreshes frequently, while other worktrees sync periodically to keep badges current. Polling pauses when the Agent Manager panel is hidden.
 
+### PR Panel
+
+When the selected worktree branch has an associated pull request, the toolbar shows a pull-request button (labeled with the PR number) next to the diff button. Click it to open a panel alongside the chat with:
+
+- The PR title, number, and state, plus the branch it merges into its parent branch
+- A summary of CI checks, review status, and unresolved comments
+- Reviewers and their review states
+- The PR description
+- CI checks with per-check status and duration, each with a link to open the check in the browser
+- Review comments, each with the diff hunk it was left on and actions to send the comment to the agent, resolve the thread, copy it, open the file, or open it on GitHub
+
+Click the link icon in the panel header to open the PR in your browser. The panel refreshes through the same `gh` polling as the badges, so it requires the GitHub CLI to be installed and authenticated.
+
+#### Review comments
+
+Each review comment shows the author, the file and line it applies to, and the code diff hunk the comment was left on, so you can read feedback without opening the PR in a browser. Threads include their replies.
+
+Unresolved threads stay expanded. Threads left on outdated code start collapsed and are marked **Outdated**. Resolved threads collapse into a **Resolved (N)** group at the bottom of the comments section — expand the group to see them, and use **Unresolve** on a comment to reopen its thread.
+
+Each comment card offers these actions:
+
+- **Send to agent** — sends the comment, with its diff context and replies, to the agent as a structured review comment so it can address the feedback in the worktree. Sent comments show a **Sent** badge.
+- **Resolve** / **Unresolve** — resolves or reopens the corresponding GitHub review thread directly from the panel. Resolving writes to GitHub through `gh`; if it fails (for example, because of missing permissions), an error is shown on the comment.
+- **Copy comment** — copies the comment as Markdown.
+- **Open file** — opens the file the comment applies to in the editor.
+- **Open on GitHub** — opens the comment on GitHub in your browser.
+
+To hand all outstanding feedback to the agent at once, click **Send N unresolved to agent** at the top of the comments section. When a terminal is active in the side panel, the button sends the comments to that terminal instead.
+
+Click the comments row in the PR summary at the top of the panel to jump straight to the comments section. On long PRs, a floating **↑** button appears once you scroll down and scrolls back to the top.
+
 ### Creating a New Worktree Session
 
 1. Click **New Worktree** or press `Cmd+N` (macOS) / `Ctrl+N` (Windows/Linux) to open the new worktree dialog
@@ -243,10 +274,45 @@ The Branch scope also has a base-branch picker next to it for overriding the com
 
 See [Agent Manager Workflows](/docs/automate/agent-manager-workflows#merging-worktree-and-parent-branch) for the full integration story, including when to apply locally vs. merge directly vs. open a pull request.
 
+### Edit Previews
+
+Edit, write, and `apply_patch` changes made in an Agent Manager session open in the side panel instead of a separate editor tab. Clicking the tool's file name expands the change inline in the transcript, while the open-diff action shows the full change in the panel, sharing the inspector area with the diff, PR, subagent, and terminal views.
+
+- Multi-file `apply_patch` payloads open every changed file, each sized to its own rendered diff
+- The preview keeps the unified or split diff style you last selected in the review view
+
+Outside Agent Manager, edit previews continue to open in a standalone diff editor tab.
+
+## Subagents Panel
+
+When an agent delegates work to a subagent, the subagent's tool block in chat shows an **Open sub-agent in panel** button. Clicking it opens the child session in the **Subagents** panel, which shares the side inspector area with the diff, PR, documents, and terminal views.
+
+- Each opened subagent gets its own tab, so you can inspect several child sessions in parallel while the parent session keeps running
+- Drag tabs to reorder them, close a tab with its close button or middle-click, or right-click a tab for **Close others**
+- `Cmd+W` (macOS) / `Ctrl+W` (Windows/Linux) closes the active subagent tab while the panel is visible
+- The subagent chat is read-only — it shows the child's transcript without taking over the parent session
+
+Subagents launched in background mode also appear in a collapsible strip in the chat header, so they stay visible after their task card scrolls away. See [Background agents](/docs/code-with-ai/agents/chat-interface#background-agents) for details.
+
+## Documents Panel
+
+Markdown and text files referenced in chat — such as plan files and other generated artifacts — open in a dedicated **Documents** view instead of a plain editor, so you can read and review them without leaving the session view.
+
+- **Agent Manager:** documents open as per-worktree tabs in the side panel, sharing the inspector area with the diff, PR, subagent, and terminal views. A documents button appears in the toolbar once the current worktree has open documents.
+- **Sidebar:** documents open in a **Documents** editor tab.
+
+The view renders Markdown by default, with a toggle to show the raw source. Images render inline; binary and oversized files are rejected with an explanatory message instead of loading. Changed Markdown files in the diff panel also have a **Preview document** button in the file header.
+
+### Review comments
+
+Select lines in a rendered document to draft an inline comment. Comments can be edited or deleted, and sent to the active session individually with **Send to chat** or all at once with **Send all to chat** (`Cmd+Enter` on macOS / `Ctrl+Enter` on Windows/Linux), so the agent can address your feedback on the document.
+
 ## Terminals
 
 Each session has a dedicated terminal rooted in the session's worktree directory. Press `Cmd+/` (macOS) / `Ctrl+/` (Windows/Linux) to focus the terminal for the active session. If the embedded terminal is already visible but the prompt has focus, the same shortcut focuses the terminal without hiding it. Press it again while the terminal has focus to hide the panel.
 
+Type `@terminal` in the Agent Manager chat to attach the focused terminal's output to your message, including embedded Run and Setup terminal tabs. In the sidebar, `@terminal` uses your active VS Code terminal instead.
+
 ### Choosing the Terminal Destination
 
 The toolbar's terminal button is a split button: click it to open a terminal, or use its dropdown to choose where terminals open:

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

@@ -81,6 +81,18 @@ Double-click the current session title at the top of the chat to edit it inline.
 
 You can also rename local sessions from **History** using the edit button or the session's context menu.
 
+### Background agents
+
+When the agent delegates work to subagents in the background, a collapsible strip in the chat header lists each background agent with its status — Running, Done, Cancelled, or Error — so they stay visible after their task card scrolls away. The same strip appears in the sidebar and in Agent Manager, scoped to the current session.
+
+Expand the strip to:
+
+- **Open** an agent's transcript — a read-only sub-agent viewer tab in the sidebar, or the Subagents panel in Agent Manager
+- **Stop** a running agent, or **Dismiss** finished agents individually or with **Clear finished**
+- Spot agents waiting on you — permission and question requests are flagged with **Needs input**
+
+While a foreground subagent is blocking the session, a **Continue in background** button in the strip lets it finish asynchronously instead.
+
 {% /tab %}
 {% tab label="CLI" %}
 

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

@@ -23,12 +23,14 @@ Type `@` in the chat input to get autocomplete suggestions. You can mention:
 | Mention | Description | Example |
 |---|---|---|
 | **File** | Attach a file's contents to your message | `@src/utils.ts` |
-| **Terminal** | Include your active VS Code terminal output | `@terminal` |
+| **Terminal** | Include terminal output | `@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 |
 
 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.
 
+In the sidebar, `@terminal` captures your active VS Code terminal. In an [Agent Manager](/docs/automate/agent-manager) session, it captures the focused Agent Manager terminal instead, including embedded Run and Setup terminal tabs.
+
 ### Referencing Past Chats
 
 Choosing **Past chats** from the `@` menu opens a searchable picker of sessions in the current workspace and related Git worktrees, including Agent Manager worktrees, ordered by recency. Search matches session titles and worktree names. Selecting a session inserts a highlighted mention token; when you send the message, that session's current chat history is added as context so the agent can build on the earlier conversation. Clicking the mention token opens the referenced session.

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

@@ -35,12 +35,12 @@ Add custom models under the `provider.<provider_id>.models` key in your config f
 - **Provider API** — The protocol used by the provider. Use **OpenAI Responses** for OpenAI and xAI models. Use **Anthropic Messages** for Anthropic and MiniMax models. **OpenAI Compatible** is the default for other OpenAI Chat Completions-compatible endpoints.
 - **Base URL** — The provider's API endpoint (e.g., `https://api.myprovider.com/v1`). When a valid URL is entered, Kilo automatically fetches available models from the endpoint if it exposes an OpenAI-compatible models endpoint.
 - **API key** — Your provider's API key. Optional — leave empty if you manage authentication via headers.
-- **Models** — Add models manually by ID and display name, or select from the auto-fetched list that appears after entering a valid base URL.
+- **Models** — Add models manually by ID and display name, or select from the auto-fetched list that appears after entering a valid base URL. Each model has **Reasoning** and **Image** checkboxes; use **Toggle reasoning for all** and **Toggle image for all** above the list to flip every model at once.
 - **Headers** (optional) — Add custom HTTP headers as key-value pairs if your provider requires them.
 
 4. Click **Submit** to save. Your custom provider appears in the provider list and its models become available in the model picker.
 
-To edit an existing custom provider, click the **Edit provider** button next to it in the connected providers section.
+To edit an existing custom provider, click the **Edit provider** button next to it in the connected providers section. From the edit dialog, click **Edit advanced settings in the JSON config file** to open the provider's entry in `kilo.jsonc` for options the dialog doesn't expose, such as `variants`.
 
 For additional model configuration (token limits, tool calling, reasoning, variants), edit the `kilo.jsonc` config file directly — see the **CLI** tab for the format.
 
@@ -93,6 +93,8 @@ All fields are optional. When a model ID matches one already in the built-in cat
 | `provider` | `object` | Override `{ npm?, api? }` — the AI SDK package or base API URL for this model |
 | `variants` | `object` | Named variant configurations (e.g., different reasoning efforts) |
 
+When a model has `reasoning: true` on a provider using the OpenAI Compatible, OpenAI Responses, or Anthropic Messages API and no variants are configured or detected, Kilo automatically offers the standard reasoning efforts — `none`, `low`, `medium`, `high`, `xhigh`, and `max` — in the variant selector. Any `variants` you configure take precedence over this automatic set.
+
 ### Modalities (modalities)
 
 The `modalities` object declares which content types the model can receive and produce. It is optional — omit it to use defaults from the catalog or fallback to text-only. When `modalities` is provided, both `input` and `output` arrays are required. Each array can include `text`, `image`, `audio`, `video`, or `pdf`.

packages/kilo-docs/pages/code-with-ai/features/speech-to-text.md

@@ -41,7 +41,7 @@ Enable and sign in to the Kilo provider to use voice input in prompt fields. Req
 
 ## Choose a model
 
-You can optionally choose a transcription model in **Settings** > **Models** > **Speech to Text Model**. Kilo stores this choice as `experimental.speech_to_text_model` in your global Kilo CLI config (`~/.config/kilo/kilo.jsonc`).
+You can optionally choose a transcription model in **Settings** > **Models** > **Speech to Text Model**. Kilo stores this choice as `experimental.speech_to_text_model` in your global Kilo CLI config (`~/.config/kilo/kilo.jsonc`). If you have not chosen a model, transcription uses NVIDIA Parakeet TDT 0.6B v3.
 
 The model list is discovered from the Kilo Gateway and reflects the transcription models available to your account or organization, so newly available models appear automatically.
 

packages/kilo-docs/pages/code-with-ai/platforms/cli.md

@@ -136,6 +136,7 @@ The `kilo console` command and its browser interface are deprecated and will be
 | Command | Aliases | Description |
 |---|---|---|
 | `/profile` | `/me`, `/whoami` | View your Kilo Gateway profile |
+| `/usage` | `/plans`, `/quota` | View provider plans and quota windows (Kilo Pass, Kilo-managed plans, and direct MiniMax Token Plans) |
 | `/teams` | `/team`, `/org`, `/orgs` | Switch between Kilo Gateway teams |
 | `/remote` | - | Toggle remote mode for Cloud Agent access |
 
@@ -642,6 +643,31 @@ kilo --continue
 - Cannot be used with a prompt argument
 - Only works when there's at least one previous session in the workspace
 
+## Git Worktrees
+
+Run Kilo in an isolated git worktree instead of your main checkout. Worktrees are created at `.kilo/worktrees/<name>` inside the primary checkout with a matching branch, and the directory is added to `.git/info/exclude` so it stays out of `git status`. This is the same location the VS Code extension's [Agent Manager](/docs/automate/agent-manager) uses, so both surfaces share worktrees.
+
+```bash
+# Create (or reuse) a worktree named "feature-x" and start the TUI in it
+kilo --worktree feature-x
+```
+
+Names are normalized to a lowercase slug. Reusing a name opens the existing worktree. Run `--worktree` from the primary checkout — creating a worktree from inside another worktree is refused.
+
+### Managing Worktrees
+
+| Command | Description |
+|---|---|
+| `kilo worktree create <name>` | Create (or reuse) a worktree and print its path |
+| `kilo worktree list` | List the current project's worktrees |
+| `kilo worktree remove <name>` | Remove a worktree, deleting its branch too |
+
+`kilo worktree create` prints only the resolved path on stdout, so scripts can do `cd "$(kilo worktree create foo)"`.
+
+### Resuming Sessions Across Worktrees
+
+Resuming an explicit session with `--session <id>` starts Kilo in the worktree where that session was originally created, if the worktree still exists.
+
 ## Remote Connections
 
 Remote Connections let you access your local CLI sessions from the Cloud Agents web interface. Requires [Kilo Gateway](/docs/gateway) connection.