You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: auto-sync vscode with merged PRs (through 2026-10-23) - #15193
This PR keeps kilo.ai/docs in sync with features merged to Kilo-Org/cloud and Kilo-Org/kilocode. Every change below links to the merged PR it documents.
Derivation: Derived from the repository layout. A product surface is a package under packages/ that ships a distinct client, plugin, backend, or hosted service: cli = packages/opencode/ + packages/tui/ + packages/server/ + packages/sdk/ + packages/plugin/; vscode = packages/kilo-vscode/ + packages/kilo-web-ui/ + packages/kilo-ui/; jetbrains = packages/kilo-jetbrains/; gateway = packages/kilo-gateway/; web = packages/kilo-console/ + packages/kilo-indexing/ + packages/kilo-memory/ + packages/kilo-sandbox/. Docs route from the IA tree packages/kilo-docs/pages/ plus docs/jetbrains-vscode-settings-parity.md: each surface lists the pages sections that document it, and the per-platform pages under packages/kilo-docs/pages/code-with-ai/platforms/ map to the matching extension surface (the vscode/ directory to vscode, jetbrains.md to jetbrains). A doc path belongs to the surface with the longest matching prefix; a path that matches none of those prefixes falls to other (the explicit other prefixes are listed under other.docs). The cloud surfaces are derived the same way from the Kilo-Org/cloud layout: cloud-mobile = apps/mobile/, cloud-web = apps/web/, cloud-extension = apps/extension/, and cloud-agent = the cloud-agent packages under packages/ (packages/cloud-agent-sdk/ + packages/cloud-agent-profile/). A cloud source names its repository while a bare string still means this repository. The pages under packages/kilo-docs/pages/collaborate/ document the cloud web app (app.kilo.ai: teams dashboard, billing, SSO, adoption dashboard), so they route to cloud-web. No page under packages/kilo-docs/pages/ documents the browser side-panel extension yet, so cloud-extension lists no docs prefix.
Paths that fall to other: packages/kilo-docs/pages/community/, packages/kilo-docs/pages/contributing/, packages/kilo-docs/LEARNINGS.md, docs/
How the two were computed: Reviewers for vscode are ranked from git history over packages/kilo-vscode/, packages/kilo-web-ui/, packages/kilo-ui/ (a commit 180 days old counts half as much, half-life 180 days). Bots (author type "Bot" or a login matching /[bot]$/i) and people without admin, write, or maintain permission are excluded.
Adds an aws_bedrock credential type to the internal admin-only Custom LLMs page (apps/web/src/app/admin/custom-llms, custom_llm2 table) that Kilo staff use to define gateway provider endpoints. This admin surface has no page anywhere in packages/kilo-docs (the only mentions of custom LLM endpoints are in contributing/architecture/cloud-security.md), so there is no user-facing page to update, and the new option is internal admin configuration rather than public product behavior. The existing AWS Bedrock IAM documentation in getting-started/byok.md covers BYOK keys, a separate feature, so it is not the right target.
Graduates custom auto routers (kilo-auto/custom/*) to all users and deletes the kilo-auto-custom-routers release flag. The docs already present custom routers as available: code-with-ai/agents/auto-model.md documents the Custom auto routers section and the kilo auto router/eval commands (mirrored in platforms/cli-reference.md) with no flag, plan, or availability caveat, and no other page references the removed isCustomRoutersEnabled/hasCustomRoutersAccess/hasLegacyPoolAccess gating. The user-facing documentation is therefore already accurate and needs no change.
Mobile bug fix correcting the no-organization deep-link state; no new command, setting, or workflow.
(bot) Generated by the docs-sync workflow. Humans review and merge; while this PR stays open, the next daily run appends new changes here. Branch: docs/auto-sync-2026-10-23.
Docs-only change adding a "Multi-root workspaces" section. Verified the described behavior against the shipped implementation (KiloProvider.sendWorkspaceScope in packages/kilo-vscode/src/KiloProvider.ts:702, WorkspaceScopeHint.tsx, and the session.workspaceScope.* i18n strings): the hint is dismissible, dismissal is keyed to the first folder's path, it only shows for multi-folder windows on non-explicit hosts, and Agent Manager/project hosts are excluded. The internal link /docs/automate/agent-manager-projects resolves to an existing page, and the heading uses sentence case per the style guide.
github-actionsBot
changed the title
docs: auto-sync vscode with merged PRs (through 2026-10-17)
docs: auto-sync vscode with merged PRs (through 2026-10-20)
Oct 20, 2026
github-actionsBot
changed the title
docs: auto-sync vscode with merged PRs (through 2026-10-20)
docs: auto-sync vscode with merged PRs (through 2026-10-21)
Oct 21, 2026
github-actionsBot
changed the title
docs: auto-sync vscode with merged PRs (through 2026-10-21)
docs: auto-sync vscode with merged PRs (through 2026-10-22)
Oct 22, 2026
github-actionsBot
changed the title
docs: auto-sync vscode with merged PRs (through 2026-10-22)
docs: auto-sync vscode with merged PRs (through 2026-10-23)
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated docs sync — 2026-10-23
This PR keeps kilo.ai/docs in sync with features merged to Kilo-Org/cloud and Kilo-Org/kilocode. Every change below links to the merged PR it documents.
2026-10-22T07:08:53.354Z→2026-10-22T20:43:51.999ZSurface:
vscodeother(the explicit other prefixes are listed under other.docs). The cloud surfaces are derived the same way from the Kilo-Org/cloud layout: cloud-mobile = apps/mobile/, cloud-web = apps/web/, cloud-extension = apps/extension/, and cloud-agent = the cloud-agent packages under packages/ (packages/cloud-agent-sdk/ + packages/cloud-agent-profile/). A cloud source names its repository while a bare string still means this repository. The pages under packages/kilo-docs/pages/collaborate/ document the cloud web app (app.kilo.ai: teams dashboard, billing, SSO, adoption dashboard), so they route to cloud-web. No page under packages/kilo-docs/pages/ documents the browser side-panel extension yet, so cloud-extension lists no docs prefix..github/docs-sync/surfaces.jsoncli,vscode,jetbrains,gateway,web,cloud-mobile,cloud-web,cloud-extension,cloud-agent,otherpackages/kilo-vscode/,packages/kilo-web-ui/,packages/kilo-ui/packages/kilo-docs/pages/code-with-ai/platforms/vscode/other:packages/kilo-docs/pages/community/,packages/kilo-docs/pages/contributing/,packages/kilo-docs/LEARNINGS.md,docs/vscodeare ranked from git history overpackages/kilo-vscode/,packages/kilo-web-ui/,packages/kilo-ui/(a commit 180 days old counts half as much, half-life 180 days). Bots (author type "Bot" or a login matching /[bot]$/i) and people without admin, write, or maintain permission are excluded.Changes
Pending — will retry
Considered, no docs change needed
(bot) Generated by the docs-sync workflow. Humans review and merge; while this PR stays open, the next daily run appends new changes here. Branch:
docs/auto-sync-2026-10-23.