Skip to content

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

Merged
lambertjosh merged 6 commits into
mainfrom
docs/consolidate-auto-sync-2026-09-14
Sep 15, 2026
Merged

lambertjosh merged 6 commits into
mainfrom
docs/consolidate-auto-sync-2026-09-14

Conversation

@lambertjosh

@lambertjosh lambertjosh commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

Why

The older docs-sync rollovers started fresh from main after conflicts rather than carrying forward unmerged documentation. This consolidates their useful changes and reviewed corrections onto current main so they can be reviewed together.

Supersedes only #13404, #13572, #13725, #13989, and #14043.

Scope

The recent per-product PRs #14128, #14129, #14130, #14131, #14132, and #14133 are intentionally excluded: they already have assigned reviewers, and the Gateway PR has an approval. Contributions unique to those PRs have been removed. Overlapping topics that were already in the five older proposals remain here.

Current implementation and existing reference pages take precedence over generated wording. Preserve the source-verified corrections for push permissions, shared worktrees, setup timing, browser prerequisites, saved-file limitations, explicit model overrides, and account/organization procedures. Use concise links instead of duplicate explanations and remove obsolete claims and low-value implementation details.

Clarify that browser_open is the local-app preview tool; websearch, webfetch, and separately configured browser MCP tools provide other web capabilities.

The closed #13223 and its historical incident-export page are not revived. This changes documentation only, not runtime code or docs-sync automation. Original PRs and branches remain intact.

Reconcile the five unmerged rolling docs PRs and six per-surface replacements against current main. Retain reviewed corrections and source-verified user workflows, use existing reference pages instead of duplicated sections, and remove outdated guarantees and implementation trivia.
@vercel

vercel Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs (docs-staging) Ready Ready Preview Sep 15, 2026 2:36am UTC

Request Review

Limit the consolidation to the five older rollover PRs, retaining overlap and source-verified corrections. Remove contributions unique to the six recent per-product PRs because they already have assigned reviewers. Clarify that browser_open is a local preview tool, not a restriction on websearch, webfetch, or browser MCP tools.
@lambertjosh lambertjosh changed the title docs(kilo-docs): consolidate reviewed documentation updates docs(kilo-docs): consolidate older docs-sync rollovers Sep 14, 2026
Comment thread packages/kilo-docs/pages/getting-started/byok.md
Comment thread packages/kilo-docs/pages/automate/integrations.md Outdated
@kilo-code-bot

kilo-code-bot Bot commented Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Re-verified the incremental change at c49a8e62: packages/kilo-docs/pages/getting-started/byok.md now uses the Cloud Gateway picker label Azure Foundry (experimental) consistently, in both the supported-provider list and the renamed configuration heading, so the earlier provider-naming mismatch is resolved. No other docs, nav, or anchor references point at the old Azure OpenAI configuration heading.

Files Reviewed (1 file)
  • packages/kilo-docs/pages/getting-started/byok.md
Previous Review Summaries (2 snapshots, latest commit 95659b1)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 95659b1)

Status: No Issues Found | Recommendation: Merge

The two previous suggestions were re-verified and are resolved in 0d20561bf9: the BYOK provider list now ties Azure OpenAI to its picker label Azure Foundry (experimental), and the Bitbucket note now matches the Cloud Agent page (organization Integrations page, web and mobile). The incremental changes correctly move Kilo Swarm to on-by-default with its toggle under Settings > Agent Behaviour, which matches packages/opencode/src/kilocode/board/enabled.ts, experimentalSharedAgentBoard defaulting to true in runtime-flags.ts, and the switch added to AgentBehaviourTab.tsx.

Files Reviewed (8 files)
  • packages/kilo-docs/pages/automate/agent-manager.md
  • packages/kilo-docs/pages/automate/integrations.md
  • packages/kilo-docs/pages/automate/tools/index.md
  • packages/kilo-docs/pages/code-with-ai/agents/orchestrator-mode.md
  • packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
  • packages/kilo-docs/pages/customize/custom-subagents.md
  • packages/kilo-docs/pages/getting-started/byok.md
  • packages/kilo-docs/pages/getting-started/settings/index.md

Previous review (commit 8d8267f)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 2

Reviewed the consolidated docs-only diff (26 files) at HEAD 8d8267f. Internal anchors and newly referenced pages (e.g. keep-awake, notifications) resolve, and the new CLI claims (/about with c copy diagnostics, --prompt-stdin, the exit-1 no-assistant-message string, the 100,000-character stdin limit, experimental.task_model_selection) match the implementation.

Issue Details (click to expand)

SUGGESTION

File Line Issue
packages/kilo-docs/pages/getting-started/byok.md 105 Instruction says to select Azure Foundry (experimental), but the provider list in the same file says Azure OpenAI and other docs use Kilo's native Azure provider. Align the name.
packages/kilo-docs/pages/automate/integrations.md 166 States Bitbucket repository selection is mobile-app-only, which conflicts with the updated Cloud Agent page describing GitHub/GitLab/Bitbucket repository support and Integrations-tab connection. Reconcile.
Files Reviewed (26 files)
  • packages/kilo-docs/pages/automate/agent-manager-workflows.md
  • packages/kilo-docs/pages/automate/agent-manager.md
  • packages/kilo-docs/pages/automate/code-reviews/github.md
  • packages/kilo-docs/pages/automate/code-reviews/overview.md
  • packages/kilo-docs/pages/automate/integrations.md - 1 issue
  • packages/kilo-docs/pages/automate/tools/index.md
  • packages/kilo-docs/pages/code-with-ai/agents/context-mentions.md
  • packages/kilo-docs/pages/code-with-ai/agents/model-selection.md
  • packages/kilo-docs/pages/code-with-ai/agents/orchestrator-mode.md
  • packages/kilo-docs/pages/code-with-ai/agents/using-agents.md
  • packages/kilo-docs/pages/code-with-ai/platforms/cli-reference.md
  • packages/kilo-docs/pages/code-with-ai/platforms/cli.md
  • packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
  • packages/kilo-docs/pages/code-with-ai/platforms/jetbrains.md
  • packages/kilo-docs/pages/code-with-ai/platforms/mobile.md
  • packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md
  • packages/kilo-docs/pages/collaborate/enterprise/sso.md
  • packages/kilo-docs/pages/collaborate/teams/team-management.md
  • packages/kilo-docs/pages/customize/context/context-condensing.md
  • packages/kilo-docs/pages/customize/custom-instructions.md
  • packages/kilo-docs/pages/deploy-secure/security-reviews.md
  • packages/kilo-docs/pages/gateway/models-and-providers.md
  • packages/kilo-docs/pages/getting-started/byok.md - 1 issue
  • packages/kilo-docs/pages/getting-started/faq/account-and-integration.md
  • packages/kilo-docs/pages/getting-started/settings/auto-approving-actions.md
  • packages/kilo-docs/pages/getting-started/settings/index.md

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash · Input: 33K · Output: 7.7K · Cached: 370.4K

Review guidance: REVIEW.md from base branch main

Match Azure Gateway BYOK naming to the Cloud picker, document organization Bitbucket support on both web and mobile, and remove Swarm setup from the deprecated Orchestrator page.

This branch was successfully deployed

1 active deployment
docs-staging – docs — c49a8e62 Deployed Sep 15, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants