From b40662a835ff74cbf51e8b6f2ba807cf2429cc58 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 10 Sep 2026 07:36:09 +0000 Subject: [PATCH 1/2] docs: sync with merged PRs (2026-09-10) --- .../kilo-docs/pages/automate/agent-manager.md | 31 +++++++++++++++++- .../pages/automate/code-reviews/github.md | 7 +++- .../pages/code-with-ai/platforms/cli.md | 9 ++++++ .../code-with-ai/platforms/cloud-agent.md | 11 +++++++ .../code-with-ai/platforms/vscode/index.md | 14 ++++++++ .../kilo-docs/pages/getting-started/byok.md | 32 +++++++++++++++++++ .../pages/getting-started/settings/index.md | 15 +++++++++ 7 files changed, 117 insertions(+), 2 deletions(-) diff --git a/packages/kilo-docs/pages/automate/agent-manager.md b/packages/kilo-docs/pages/automate/agent-manager.md index 78b9e801bad1..3645f8c79688 100644 --- a/packages/kilo-docs/pages/automate/agent-manager.md +++ b/packages/kilo-docs/pages/automate/agent-manager.md @@ -99,7 +99,7 @@ In a managed worktree's chat, type `/update-from-base` and select the action to The saved base stays the same if you switch branches in Local or change the project's default base. For example, a worktree created from `main` still updates from `main` when Local has `release` checked out. If you switch branches inside the managed worktree, the agent updates that worktree's current branch, not its original branch. Select the intended worktree before running the command; it does not update Local. -The agent uses the recorded remote, or the saved base branch's upstream if no remote was recorded. It asks for a source if the base is local-only or unavailable. The request prohibits stashing, discarding uncommitted work, and pushing. Existing merge or rebase operations and blocking dirty changes require your input. Normal tool approvals still apply. +The agent uses the recorded remote, or the saved base branch's upstream if no remote was recorded. It asks for a source if the base is local-only or unavailable. The request prohibits stashing and discarding uncommitted work. When [push fixes](#pushing-fixes-to-the-pull-request) is enabled (the default) and the worktree has a pull request, the agent pushes the branch after a clean merge so the pull request updates; otherwise the request prohibits pushing. Existing merge or rebase operations and blocking dirty changes require your input. Normal tool approvals still apply. ### Worktree Location @@ -191,6 +191,35 @@ Use the actions on an expanded thread to: The panel header also provides **Copy PR link**, **Open in browser**, and **Close**. Sending a comment gives it to Kilo as review context. It does not post a reply to GitHub. The panel intentionally has no reply composer; write replies in GitHub. +#### Pushing fixes to the pull request + +When you send pull request CI failures or review comments to the agent from the PR panel — or update a worktree from its base while the worktree has a pull request — the agent is asked to validate its fix with local checks, then commit and push to the PR branch so the pull request updates and CI runs again. The agent is instructed never to force-push, and normal permission prompts still confirm each commit and push. + +This behavior is controlled by the **Push Pull Request Fixes** toggle under **Settings → Agent Behaviour** (the `kilo-code.new.agentManager.pushFixes` setting), and it is on by default. Turn it off to keep fixes local for manual commit and push. Local inline review comments you send from the diff panel stay manual either way. + +#### Merge readiness and merging + +The PR panel header shows the approval count with reviewer avatars, and a merge readiness section summarizes whether GitHub can merge the pull request: + +| State | Meaning | +|---|---| +| Ready to merge | GitHub reports a clean merge state | +| Merging blocked | Branch protection requirements are not met yet | +| Branch is behind the base branch | The base branch has newer commits | +| Checks are failing | Required checks are failing | +| Merge conflicts | The branch conflicts with the base branch | +| Draft pull request | Mark the PR ready for review before merging | +| Checking mergeability | GitHub has not computed mergeability yet | + +The available actions depend on the state: + +- **Merge method menu** — merge with a merge commit, squash, or rebase. Only the methods the repository allows are listed, and the last method you used is remembered per repository. +- **Enable auto-merge / Disable auto-merge** — shown when the repository allows auto-merge. GitHub merges the pull request automatically once its requirements are met, with the selected method. +- **Update branch** — merge the latest base branch changes into the PR branch via GitHub when the branch is behind. +- **Fix with Kilo** — send the conflicting file list to the agent to resolve merge conflicts. Conflicting files are detected without changing your worktree and shown in a bounded list. + +Merges run remotely on GitHub. The panel refuses stale actions when the pull request changed since the data was loaded; refresh the panel and try again in that case. + ### Creating a New Worktree Session 1. Click **New Worktree** or press `Cmd+N` (macOS) / `Ctrl+N` (Windows/Linux) to open the new worktree dialog diff --git a/packages/kilo-docs/pages/automate/code-reviews/github.md b/packages/kilo-docs/pages/automate/code-reviews/github.md index 753a25ffbeb3..eae410de2653 100644 --- a/packages/kilo-docs/pages/automate/code-reviews/github.md +++ b/packages/kilo-docs/pages/automate/code-reviews/github.md @@ -79,6 +79,10 @@ When a review triggers: The repository list is synced from GitHub and can be refreshed from the configuration page. +### Per-repository overrides + +You can turn automated PR reviews on or off for an individual repository without changing the overall configuration. A repository-level setting takes precedence over the installation default, so you can disable reviews for one noisy repository — or keep a single repository enabled while the default is off. When reviews are disabled for a repository, Kilo skips incoming pull requests for it and no review is started. + ## Troubleshooting ### Reviews are not triggering @@ -86,7 +90,8 @@ The repository list is synced from GitHub and can be refreshed from the configur 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 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 automated reviews are not turned off for that repository by a per-repository override +5. Confirm the PR is not a draft ### Reviews are failing diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md index df3ebef31d24..c7fe00232202 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md @@ -137,6 +137,7 @@ The `kilo console` command and its browser interface are deprecated and will be | `/editor` | - | Open external editor | | `/auto-approve` | `/autoapprove`, `/approve-all`, `/approveall` | Toggle auto-approve mode for all permission prompts (saved to global config) | | `/privacy` | - | Toggle privacy mode (blurs PII in the TUI) | +| `/caffeinate` | `/caffenate` | Toggle Keep Awake (prevent system sleep while agents work) | | `/exit` | `/quit`, `/q` | Exit the app | #### Kilo Gateway Commands (when connected) @@ -238,6 +239,14 @@ The `attention.sound_pack` setting selects a sound pack registered by a TUI plug There is no notification slash command or command-palette toggle. Use `tui.json` or `tui.jsonc` so all attention behavior is controlled by the same configuration. +## Keep Awake + +Keep Awake prevents your computer from sleeping while Kilo sessions are busy or retrying. It is off by default; toggle it with the `/caffeinate` command (also available as `/caffenate`) or the **Enable Keep Awake** command-palette action. + +- The first time you enable it, Kilo asks for confirmation. Keep Awake prevents system sleep only — it does not keep the display on or disable screen locking, and agents may continue to access files, network services, and available credentials while the computer is locked. +- The sleep inhibitor activates when a session is busy or retrying and releases when sessions are idle. +- The inhibitor is cleaned up when you exit the CLI. A toast message confirms enable and disable, and reports runtime failures. + ## Slash Commands The CLI's interactive mode supports slash commands for common operations. The main commands are documented above in the [Interactive Slash Commands](#interactive-slash-commands) section. diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md index ddbe85f30798..bdf4a794e317 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md @@ -75,6 +75,17 @@ kilo cloud start --prompt "Fix the flaky login test" --repo Kilo-Org/kilocode - Expect slightly longer setup after idle periods - Inactive cloud agent sessions are deleted after **7 days** during the beta, expired sessions are still accessible via the CLI +## Workspace Folders + +Group your Cloud Agent workspaces into folders in the sidebar. Folders are private to you and are not shared with your organization. + +- Create a folder with a name and an optional color, then move workspaces into it by dragging them onto the folder. +- Rename, recolor, reorder, collapse, or delete folders from the folder menu. Deleting a folder does not delete the workspaces inside it — they move back to the ungrouped list. + +## Viewing Worktree Files + +Each Cloud Agent session saves the contents of the files it changed. Select a file from the session's change list to open it in a read-only file tab next to the chat and terminal tabs. The file pane shows the saved content or a diff of the change, and can reload the latest saved revision without starting the workspace. + ## Agent Environment Profiles Agent environment profiles are reusable bundles of environment settings for cloud-agent sessions. A profile can include: diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md index e264507d77a0..78ad8d2251f3 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md @@ -31,6 +31,7 @@ Key features include: - **[Custom Subagents](/docs/customize/custom-subagents)** — Define specialized sub-agents for the `task` tool - **Charts** — Ask for a chart or plot and get an inline data visualization in the chat - **Open in Tab** — Pop the chat out into a full editor tab +- **Keep Awake** — Optionally prevent system sleep while agents work - **Transcript export:** Save complete local session transcripts as Markdown files - **Sub-Agent Viewer** — Read-only panels for viewing child agent sessions - **Legacy Migration** — Automatic migration wizard for VSCode extension settings @@ -57,6 +58,19 @@ Use these controls in the expanded strip: - **Clear finished** hides all agents that are no longer running. - **Continue in background** appears when a foreground subagent is running. It detaches that work so the parent session can continue while the subagent runs in the background. +## Keep Awake + +Keep Awake prevents your computer from sleeping while Kilo sessions are busy or retrying. It is off by default and is available only in a local VS Code window (not in remote workspaces). + +Toggle it in either of these ways: + +- Run `/caffeinate` in the chat prompt +- Run **Kilo Code: Toggle Keep Awake** from the Command Palette + +The first time you enable it, Kilo asks for confirmation and, in an untrusted workspace, asks you to trust the workspace first. Keep Awake prevents system sleep only — it does not keep the display on or disable screen locking, and agents may continue to access files, network services, and available credentials while the computer is locked. On Linux, it can also block manual suspend; turn Keep Awake off before suspending. + +The sleep inhibitor releases when sessions go idle, and it turns off when the VS Code window reloads. A notification explains enable, disable, and runtime failure states. + ## Shared Settings Settings apply across extension surfaces, including the sidebar and Agent Manager. The standalone CLI uses the same `~/.config/kilo/kilo.jsonc` (global) and `./kilo.jsonc` (project) files when used directly. diff --git a/packages/kilo-docs/pages/getting-started/byok.md b/packages/kilo-docs/pages/getting-started/byok.md index d3915372cba9..9c78e0a80492 100644 --- a/packages/kilo-docs/pages/getting-started/byok.md +++ b/packages/kilo-docs/pages/getting-started/byok.md @@ -24,6 +24,7 @@ Use your provider API key to route matching models through your account: - Anthropic - AWS Bedrock +- Azure OpenAI (experimental) - DeepSeek - Fireworks - Google AI Studio @@ -88,6 +89,37 @@ Your IAM user or role must have the following permissions: - `bedrock:InvokeModel` - `bedrock:InvokeModelWithResponseStream` +### Azure OpenAI configuration + +Azure OpenAI (listed as **Azure Foundry (experimental)**) requires structured JSON credentials instead of a single API key: + +```json +{ + "apiKey": "...", + "resourceName": "my-resource" +} +``` + +| Field | Description | +|---|---| +| `apiKey` | Your Azure OpenAI API key | +| `resourceName` | The subdomain of your Azure OpenAI endpoint, for example `my-resource` from `my-resource.openai.azure.com` | + +If your Azure deployments use custom names that differ from the gateway model slugs, add a `modelMappings` array that maps each gateway model slug to your deployment name: + +```json +{ + "apiKey": "...", + "resourceName": "my-resource", + "modelMappings": [ + { + "gatewayModelSlug": "openai/gpt-5.4-nano", + "customModelId": "my-gpt-5-4-nano-deployment" + } + ] +} +``` + ## How Bring Your Own Key works - When you use the **Kilo Gateway** provider, Kilo checks if there's a BYOK key for the selected model's provider. diff --git a/packages/kilo-docs/pages/getting-started/settings/index.md b/packages/kilo-docs/pages/getting-started/settings/index.md index 21eeb037d3aa..52b401ab3eb2 100644 --- a/packages/kilo-docs/pages/getting-started/settings/index.md +++ b/packages/kilo-docs/pages/getting-started/settings/index.md @@ -187,6 +187,7 @@ Available experimental settings include: - **Paste summary** - summarize large clipboard pastes before including them - **Batch tool** - allow the agent to batch multiple tool calls in one step - **Kilo Swarm** - let a main session and its task subagents share a board (off by default) +- **Claude Code Migration** - one-time import of supported global Claude Code configuration into Kilo (off by default) - **OpenTelemetry** - enable Kilo telemetry and optional OTLP export when configured Advanced options not exposed in the UI can be configured via the `experimental` key in `kilo.jsonc`: @@ -230,3 +231,17 @@ Straightforward tasks can stay solo. Enabling the board does not mean agents are **Post message** (`board_post`) stores a message on the shared board. **Read messages** (`board_read`) retrieves messages from the board explicitly. Activity notices are best-effort: a stored message does not prove that a recipient was notified, read it, or acted on it. Posting does not start or resume an agent, and normal task completion still returns results to the parent. All participants can read the board history, including messages addressed to others. Recipient selection is not a privacy boundary. Peer messages do not grant user approval or change permissions; `HOLD` and `VETO` are advisory, not controls that pause or cancel work. + +### Claude Code Migration + +Claude Code Migration is an opt-in, one-time import of supported global Claude Code configuration into Kilo. Enable **Claude Code Migration (Experimental)** in the VS Code **Experimental** settings; the migration runs once on the next backend start and never retries automatically. It is off by default. + +The migration imports the supported global subset only: + +- **Global instructions** — `~/.claude/CLAUDE.md` becomes your global `AGENTS.md` +- **Skills** — simple standalone skills from `~/.claude/skills/` +- **MCP servers** — top-level definitions from `~/.claude.json`, imported disabled so you enable them explicitly + +Existing Kilo instructions, skills, and MCP server names win on conflict, and items outside the supported subset are skipped. After the migration attempt, Kilo stops loading global Claude configuration as a fallback; project-level Claude compatibility (for example a `CLAUDE.md` in your repository) is unaffected. + +Your original Claude files are never modified or deleted, so you can keep using Claude Code alongside Kilo. A notification reports the outcome — imported, skipped, or failed per item — with a receipt on disk for the full list. From 10ca82af70c942237dc0c83a4787c3965553f284 Mon Sep 17 00:00:00 2001 From: Josh Lambert Date: Mon, 14 Sep 2026 10:34:21 -0400 Subject: [PATCH 2/2] docs(kilo-docs): correct PR fix permissions and saved previews Verify workflow behavior against #13951, #13953, and #13780; preserve sandbox-specific Git approval requirements. Check saved-file omissions against Kilo-Org/cloud#5813 and folder controls against cloud#5948. --- packages/kilo-docs/pages/automate/agent-manager.md | 10 +++++++--- packages/kilo-docs/pages/code-with-ai/platforms/cli.md | 5 ++--- .../pages/code-with-ai/platforms/cloud-agent.md | 9 +++++---- .../pages/code-with-ai/platforms/vscode/index.md | 4 ++-- .../kilo-docs/pages/getting-started/settings/index.md | 4 ++-- 5 files changed, 18 insertions(+), 14 deletions(-) diff --git a/packages/kilo-docs/pages/automate/agent-manager.md b/packages/kilo-docs/pages/automate/agent-manager.md index 3645f8c79688..112d71888a33 100644 --- a/packages/kilo-docs/pages/automate/agent-manager.md +++ b/packages/kilo-docs/pages/automate/agent-manager.md @@ -99,7 +99,9 @@ In a managed worktree's chat, type `/update-from-base` and select the action to The saved base stays the same if you switch branches in Local or change the project's default base. For example, a worktree created from `main` still updates from `main` when Local has `release` checked out. If you switch branches inside the managed worktree, the agent updates that worktree's current branch, not its original branch. Select the intended worktree before running the command; it does not update Local. -The agent uses the recorded remote, or the saved base branch's upstream if no remote was recorded. It asks for a source if the base is local-only or unavailable. The request prohibits stashing and discarding uncommitted work. When [push fixes](#pushing-fixes-to-the-pull-request) is enabled (the default) and the worktree has a pull request, the agent pushes the branch after a clean merge so the pull request updates; otherwise the request prohibits pushing. Existing merge or rebase operations and blocking dirty changes require your input. Normal tool approvals still apply. +The agent uses the recorded remote, or the saved base branch's upstream if no remote was recorded. It asks for a source if the base is local-only or unavailable. It is instructed to preserve uncommitted edits in a verified recovery copy, then restore them and their staging state after merging, without using Git stash. It asks for input if it cannot verify that recovery copy or a merge or rebase is already in progress. + +When [push fixes](#pushing-fixes-to-the-pull-request) is enabled (the default) and the worktree has a pull request, the agent is asked to push after a clean merge and successful checks; otherwise it is instructed not to push. Normal tool permissions still apply. ### Worktree Location @@ -193,7 +195,9 @@ The panel header also provides **Copy PR link**, **Open in browser**, and **Clos #### Pushing fixes to the pull request -When you send pull request CI failures or review comments to the agent from the PR panel — or update a worktree from its base while the worktree has a pull request — the agent is asked to validate its fix with local checks, then commit and push to the PR branch so the pull request updates and CI runs again. The agent is instructed never to force-push, and normal permission prompts still confirm each commit and push. +When you send pull request CI failures or review comments to the agent from the PR panel, it is asked to run local checks, then commit and push the fix so the pull request updates and CI runs again. Updating a worktree from its base can also push to its pull request. The agent is instructed never to force-push. + +Your configured tool permissions still apply. Auto-approved commands can run without another prompt; when sandboxing is active, mutating Git commands require a separate, one-shot approval. This behavior is controlled by the **Push Pull Request Fixes** toggle under **Settings → Agent Behaviour** (the `kilo-code.new.agentManager.pushFixes` setting), and it is on by default. Turn it off to keep fixes local for manual commit and push. Local inline review comments you send from the diff panel stay manual either way. @@ -216,7 +220,7 @@ The available actions depend on the state: - **Merge method menu** — merge with a merge commit, squash, or rebase. Only the methods the repository allows are listed, and the last method you used is remembered per repository. - **Enable auto-merge / Disable auto-merge** — shown when the repository allows auto-merge. GitHub merges the pull request automatically once its requirements are met, with the selected method. - **Update branch** — merge the latest base branch changes into the PR branch via GitHub when the branch is behind. -- **Fix with Kilo** — send the conflicting file list to the agent to resolve merge conflicts. Conflicting files are detected without changing your worktree and shown in a bounded list. +- **Fix with Kilo** — ask the agent to fetch and merge the worktree's saved base branch and resolve conflicts. The [Push Pull Request Fixes](#pushing-fixes-to-the-pull-request) setting controls whether it also pushes. Merges run remotely on GitHub. The panel refuses stale actions when the pull request changed since the data was loaded; refresh the panel and try again in that case. diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md index c7fe00232202..d29e3ae16b7c 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md @@ -239,13 +239,12 @@ The `attention.sound_pack` setting selects a sound pack registered by a TUI plug There is no notification slash command or command-palette toggle. Use `tui.json` or `tui.jsonc` so all attention behavior is controlled by the same configuration. -## Keep Awake +## Keep awake Keep Awake prevents your computer from sleeping while Kilo sessions are busy or retrying. It is off by default; toggle it with the `/caffeinate` command (also available as `/caffenate`) or the **Enable Keep Awake** command-palette action. - The first time you enable it, Kilo asks for confirmation. Keep Awake prevents system sleep only — it does not keep the display on or disable screen locking, and agents may continue to access files, network services, and available credentials while the computer is locked. -- The sleep inhibitor activates when a session is busy or retrying and releases when sessions are idle. -- The inhibitor is cleaned up when you exit the CLI. A toast message confirms enable and disable, and reports runtime failures. +- Your computer can sleep again when sessions are idle or you exit the CLI. ## Slash Commands diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md index bdf4a794e317..80183138a14f 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md @@ -75,16 +75,17 @@ kilo cloud start --prompt "Fix the flaky login test" --repo Kilo-Org/kilocode - Expect slightly longer setup after idle periods - Inactive cloud agent sessions are deleted after **7 days** during the beta, expired sessions are still accessible via the CLI -## Workspace Folders +## Workspace folders Group your Cloud Agent workspaces into folders in the sidebar. Folders are private to you and are not shared with your organization. - Create a folder with a name and an optional color, then move workspaces into it by dragging them onto the folder. -- Rename, recolor, reorder, collapse, or delete folders from the folder menu. Deleting a folder does not delete the workspaces inside it — they move back to the ungrouped list. +- Rename, recolor, reorder, or delete folders from the folder menu. Deleting a folder moves its workspaces back to the ungrouped list without deleting them. +- Click a folder's header to collapse or expand it. -## Viewing Worktree Files +## Viewing worktree files -Each Cloud Agent session saves the contents of the files it changed. Select a file from the session's change list to open it in a read-only file tab next to the chat and terminal tabs. The file pane shows the saved content or a diff of the change, and can reload the latest saved revision without starting the workspace. +Select a file from the session's change list to open its saved diff and, when available, full contents in a read-only tab. Binary, unsupported, or oversized files may not have a preview, and large changes can exceed the capture limit. Reloading reads the latest saved revision without starting the workspace. ## Agent Environment Profiles diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md index 78ad8d2251f3..5669b8f036b2 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md @@ -58,7 +58,7 @@ Use these controls in the expanded strip: - **Clear finished** hides all agents that are no longer running. - **Continue in background** appears when a foreground subagent is running. It detaches that work so the parent session can continue while the subagent runs in the background. -## Keep Awake +## Keep awake Keep Awake prevents your computer from sleeping while Kilo sessions are busy or retrying. It is off by default and is available only in a local VS Code window (not in remote workspaces). @@ -69,7 +69,7 @@ Toggle it in either of these ways: The first time you enable it, Kilo asks for confirmation and, in an untrusted workspace, asks you to trust the workspace first. Keep Awake prevents system sleep only — it does not keep the display on or disable screen locking, and agents may continue to access files, network services, and available credentials while the computer is locked. On Linux, it can also block manual suspend; turn Keep Awake off before suspending. -The sleep inhibitor releases when sessions go idle, and it turns off when the VS Code window reloads. A notification explains enable, disable, and runtime failure states. +Your computer can sleep again when sessions are idle. Keep Awake turns off when the VS Code window reloads. ## Shared Settings diff --git a/packages/kilo-docs/pages/getting-started/settings/index.md b/packages/kilo-docs/pages/getting-started/settings/index.md index 52b401ab3eb2..1f607b57693f 100644 --- a/packages/kilo-docs/pages/getting-started/settings/index.md +++ b/packages/kilo-docs/pages/getting-started/settings/index.md @@ -232,9 +232,9 @@ Straightforward tasks can stay solo. Enabling the board does not mean agents are All participants can read the board history, including messages addressed to others. Recipient selection is not a privacy boundary. Peer messages do not grant user approval or change permissions; `HOLD` and `VETO` are advisory, not controls that pause or cancel work. -### Claude Code Migration +### Claude Code migration -Claude Code Migration is an opt-in, one-time import of supported global Claude Code configuration into Kilo. Enable **Claude Code Migration (Experimental)** in the VS Code **Experimental** settings; the migration runs once on the next backend start and never retries automatically. It is off by default. +Claude Code Migration is an opt-in, one-time import of supported global Claude Code configuration into Kilo. Enable **Claude Code Migration** in the VS Code **Experimental** settings; the migration runs once on the next backend start and never retries automatically. It is off by default. The migration imports the supported global subset only: