docs: sync with merged PRs (2026-08-27)

2026-09-01 15:32:11 +08:00 · 2026-08-27 10:31:11 +00:00
parent bd4c27b0d1
commit ce04b2b090
9 changed files with 64 additions and 8 deletions
@@ -155,6 +155,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 every committed, staged, unstaged, and untracked change in the worktree against its recorded parent branch. This scope is offered only in Agent Manager 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.
@@ -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]`** — Review every committed, staged, unstaged, and untracked change in an Agent Manager worktree against its recorded parent branch (offered only in Agent Manager worktree sessions)
 - **`/review <commit-hash>`** — Review a specific commit
 - **`/review <PR URL or number>`** — Review a pull request

@@ -40,6 +40,10 @@ Before connecting:

 Go to your **Personal** or **Organization Dashboard**, and navigate to the [Integrations](https://app.kilo.ai/integrations) tab.

+{% callout type="note" %}
+For organizations, only Owners and Admins can add a GitHub integration. If you have another role, ask an Owner or Admin to complete the installation.
+{% /callout %}
+
 ### 2. Start the Connection Flow

 1. Click **Configure** on the GitHub panel.
@@ -163,7 +167,7 @@ Once your integrations are connected, the following features are enabled in Kilo

 ### Upcoming:

- **Bitbucket Integration**
+- **Bitbucket Integration** — currently available only for organizations when starting [Cloud Agent](/docs/code-with-ai/platforms/cloud-agent) sessions; full integration support is upcoming

 ---

@@ -171,6 +175,10 @@ Once your integrations are connected, the following features are enabled in Kilo

 ### GitHub

+For organizations, the GitHub integration page lists each installation with its connection health, repository scope (all or only selected repositories), the selected repositories, and per-installation actions. Personal accounts keep the single GitHub identity connection.
+
+An organization can connect more than one GitHub organization. Click **Add organization** on the GitHub panel and repeat the installation flow for each GitHub organization; each one appears as a separate installation with its own repository scope and actions. Adding installations requires the Owner or Admin role.
+
 From the **Integrations** page, click "Manage on GitHub" to:

 - View the GitHub account you connected
@@ -5,7 +5,7 @@ description: "Using Kilo Code in the browser"

 # {% $markdoc.frontmatter.title %}

-Cloud Agents let you run Kilo Code in the cloud from any device, without relying on your local machine. They provide a remote development environment that can read and modify your GitHub and GitLab repositories, run commands, and auto-commit changes as work progresses.
+Cloud Agents let you run Kilo Code in the cloud from any device, without relying on your local machine. They provide a remote development environment that can read and modify your GitHub, GitLab, or Bitbucket repositories, run commands, and auto-commit changes as work progresses. Bitbucket repositories are available for organizations only, not personal accounts.

 ## What Cloud Agents Enable

@@ -18,8 +18,8 @@ Cloud Agents let you run Kilo Code in the cloud from any device, without relying

 Before using Cloud Agents:

- **GitHub or GitLab Integration must be configured**
-  Connect your account via the [Integrations tab](https://app.kilo.ai/integrations) so that Cloud Agents can access your repositories.
+- **A GitHub, GitLab, or Bitbucket integration must be configured**
+  Connect your account via the [Integrations tab](https://app.kilo.ai/integrations) so that Cloud Agents can access your repositories. Bitbucket is available for organizations only.

 ## Cost

@@ -46,12 +46,12 @@ If a compute billing check fails — for example, when the paying account has in

 ## How to Use

-1. **Connect your GitHub or GitLab account** in the [Integrations](https://app.kilo.ai/integrations) tab of your personal or organization dashboard.
-2. **Select a repository** to use as your workspace.
+1. **Connect your GitHub, GitLab, or Bitbucket account** in the [Integrations](https://app.kilo.ai/integrations) tab of your personal or organization dashboard. Bitbucket is available for organizations only.
+2. **Select a repository** to use as your workspace. The repository picker groups your repositories into Recently used and per-provider sections.
 3. **Add environment variables** (secrets supported) and set optional startup commands.
 4. **Start chatting with Kilo Code.**

-Your work is always pushed to GitHub, ensuring nothing is lost.
+Your work is always pushed to your repository, ensuring nothing is lost.

 ## Starting Tasks from the CLI

@@ -34,7 +34,7 @@ The Kilo Code tool window is split into two tabs:

 When the workspace is a git repository, the chat header shows a branch dock with the current branch, a file-change summary, and worktree actions:

- **New Worktree** — create a new git worktree with its own branch and session.
+- **New Worktree** — open the New Worktree dialog, which has three tabs: **New** creates a worktree on a new branch with an optional initial prompt, **From PR** imports a GitHub pull request by URL, and **From Branch** imports an existing local branch that no worktree is using yet. Imported PR branches get git tracking set up, so `git push` and `git pull` work in the new worktree.
 - **Move to Worktree** — move the conversation and your current local changes into a dedicated worktree for isolated follow-up work. Available whenever the repository has local changes, even before the chat has a session.

 When the branch has an associated pull request, the dock shows the PR badge and title with access to the diff. Worktree actions appear only while the session is idle.
@@ -48,3 +48,9 @@ When the branch has an associated pull request, the dock shows the PR badge and
 ## Permission requests

 When the agent asks for several approvals at once, permission requests queue up instead of replacing each other. Resolve the current request to advance to the next one in the queue.
+
+## Turn failures and retries
+
+When a turn fails — for example from a provider error or missing provider credentials — the transcript ends with an error card showing the failure details and a **Retry** action. Retry replays the failed turn using the model and agent selected at that moment, so you can switch away from an unavailable provider and press **Retry** to continue the conversation.
+
+Pressing **Stop** is not treated as a failure. The transcript shows a short "Stopped" note, and the session does not get an error badge in the history, recents, or Agent Manager worktree rows.
@@ -41,6 +41,14 @@ On first launch, the app asks for your consent before enabling optional telemetr

 You can review or change your decision at any time in **Settings**. Declining optional telemetry keeps you signed in, and optional telemetry state stored on the device is stopped and discarded when you revoke consent or sign out.

+## Links and images in chat
+
+Model replies can contain links and images, and the app asks before anything loads or opens:
+
+- **Images stay hidden until you tap Load.** Each image shows its host and a **Load** button, and nothing is fetched until you tap it. Only HTTPS images can load — `http` and `data:` images show a static "HTTPS images only" chip instead.
+- **Links confirm their destination host** in a native alert before they open in the browser. Choose **Trust this host** to open that host's links directly from then on.
+- **Preferences → Trusted hosts** lists every host you have trusted, and you can revoke any of them. Trusted hosts are cleared when you sign out.
+
 ## Kilo Pass and Billing

 For Kilo Pass pricing, billing, and account management details, use the [Kilo Pass pricing page](https://kilo.ai/pricing/kilo-pass).
@@ -66,6 +74,8 @@ The new-session screen includes a **Run on** picker that chooses where your sess

 Remote sessions start with the mode and model selected on the new-session screen; older CLI versions that don't accept those fields fall back to their own defaults. The workspace is always the CLI's own checkout, so there is no repository selection — you type your first prompt in the chat after the session starts. The picker also appears in organization context, where the spawned session is attributed to the organization.

+For Cloud Agent sessions, you pick the repository the agent works on. The repository picker groups your repositories into **Recently used** and per-provider sections — GitHub, GitLab, and, for organizations, Bitbucket — and shows each repository's provider next to its name. Each provider shows its own connect prompt or error message, so a problem with one provider does not hide the repositories of another.
+
 ## Queueing follow-up messages

 The composer stays editable while the agent is working, so you don't have to wait for a session to finish before sending your next message. Type your follow-up and press **Send** to add it to the session's queue; queued messages are processed in order. While a session is streaming, **Stop** appears only when the composer is empty — with text entered, Send takes its place.
@@ -54,6 +54,10 @@ Copy the Service Provider details (Entity ID, ACS URL, and Metadata) from the Wo
 1. Set the organization policy and user provisioning settings according to your organization's needs.
 2. Configure domain policy and domain verification in WorkOS.

+{% callout type="info" %}
+WorkOS domain verification for SSO is separate from [verified-domain auto-join](/docs/collaborate/teams/team-management#joining-automatically-with-a-verified-domain), which automatically adds users with a matching email domain to your organization and does not require SSO.
+{% /callout %}
+
 After enabling SSO:

 - Invite new users with their company email domain.
@@ -23,6 +23,18 @@ Members can use the Kilo Code extension and see data on the team's usage in the

 {% image src="/docs/img/team-management/invite-member.png" alt="invite-member" width="619" caption="invite-member" /%}

+## Joining Automatically with a Verified Domain
+
+Instead of inviting each teammate individually, you can verify your organization's email domain so matching users join automatically:
+
+1. **Navigate to your Organization dashboard** and open the **Verified Domains** card
+2. **Add your company's email domain** and complete the verification steps to prove ownership
+3. Once verified, **anyone who signs in to Kilo with a matching email address** is added to the organization as a Member automatically
+
+Auto-join applies to browser sign-in, SSO sign-in, and the mobile app's native sign-in. It adds users as ordinary Members only — Owner roles still require an explicit role change. Users keep their personal account and any unrelated organization memberships, and a member who is removed from the organization is not re-added automatically.
+
+Verified domains work independently of SSO — you don't need SSO configured to use them. For SSO setup, see [SSO](/docs/collaborate/enterprise/sso).
+
 ## Removing Team Members

 When team members leave:
@@ -18,6 +18,20 @@ Your organization will become inaccessible.
 No charges will be applied.
 If you have any remaining credits in your organization, you can contact Support to request that they be moved to your personal account.

+### How do I delete my account?
+
+You can delete your personal account yourself from the [profile page](https://app.kilo.ai/profile):
+
+1. Open the **Danger Zone** card on your profile
+2. Start the deletion flow and confirm by entering your email address
+3. You are signed out once the deletion starts
+
+Account deletion is permanent. Cancel any active subscriptions before starting. When the deletion completes, you receive a confirmation email.
+
+{% callout type="note" %}
+Accounts managed by an organization cannot be deleted self-service — the Danger Zone is hidden for them. Contact your organization admin or Kilo support instead.
+{% /callout %}
+
 ## Integrations

 ### How do I unlink my GitHub account?