Repository navigation
docs: auto-sync cli with merged PRs (through 2026-10-31) - #15139
Open
github-actions[bot] wants to merge 18 commits into
Open
github-actions[bot] wants to merge 18 commits into
github-actions[bot] wants to merge 18 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Code Review SummaryStatus: 7 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (6 files)
Previous Review Summaries (8 snapshots, latest commit 90ddc55)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 90ddc55)Status: 5 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (4 files)
Fix these issues in Kilo Cloud Previous review (commit 6e62dfe)Status: 5 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (4 files)
Fix these issues in Kilo Cloud Previous review (commit 1173b37)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit ae198fc)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (3 files)
Previous review (commit 37b7a2d)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (7 files)
Previous review (commit 6092102)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous review (commit 59d20e8)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (3 files)
Previous review (commit 64354d2)lgtm Reviewed by deepseek-flash-latest · Input: 98.8K · Output: 25.1K · Cached: 4.5M Review guidance: REVIEW.md from base branch |
github-actions
Bot
changed the title
WebReflection
approved these changes
Oct 19, 2026
github-actions
Bot
changed the title
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| - `kilo auto router remove <router> <model>` — remove a client model entry | ||
| - `kilo auto eval <router>` — run the router's missing client evals locally in Docker | ||
|
|
||
| When you select a custom router, Kilo ranks the entries this machine can serve, asks the routing service for a decision, and runs the chosen model through its local provider. See the [CLI command reference](/docs/code-with-ai/platforms/cli-reference#kilo-auto) for every command and option. |
Contributor
There was a problem hiding this comment.
[SUGGESTION]: Dispatch does not always run on the local provider
KiloCustomRouter.resolve returns undefined when the router has no servable client entry, and the custom model id is then forwarded to the gateway unchanged; even with local entries, the routing decision can pick a gateway entry. So "runs the chosen model through its local provider" overstates the local path.
Suggested change
| When you select a custom router, Kilo ranks the entries this machine can serve, asks the routing service for a decision, and runs the chosen model through its local provider. See the [CLI command reference](/docs/code-with-ai/platforms/cli-reference#kilo-auto) for every command and option. | |
| When you select a custom router, Kilo sends the entries this machine can serve to the routing service for a decision and dispatches the pick — through your local provider when it is a registered client model, otherwise through the gateway. A router with no local entries stays on the gateway. See the [CLI command reference](/docs/code-with-ai/platforms/cli-reference#kilo-auto) for every command and option. |
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
|
|
||
| When you are signed in to Kilo Gateway, the CLI home screen shows the most recent unread Kilo news item, with a `(N new)` count when more than one item is unread. Select the banner to open the **News** dialog, which lists every unread item and its action links. Opening the dialog marks those items as read, and they stay hidden after a restart. Items that are not intended for the CLI are not shown. | ||
|
|
||
| The command palette has **Hide news** and **Show news** on the home screen, and the choice persists. Kilo fetches news only while you are signed in, and refetches after you sign in, sign out, or switch teams. |
Contributor
There was a problem hiding this comment.
[SUGGESTION]: News is not refetched after sign-in, sign-out, or a team switch in the current CLI
packages/opencode/src/kilocode/components/kilo-news.tsx fetches notifications once when sync.status becomes complete, guarded by fetched(), and only if Kilo is connected at that moment; it has no subscription to credential or team changes. The refetch-on-account/team-change behavior comes from the v2 port (packages/tui/src/kilocode/kilo-news.tsx), which is not in this tree, so this sentence overstates what the shipped CLI does (signing in after launch will not load news until a restart).
Suggested change
| The command palette has **Hide news** and **Show news** on the home screen, and the choice persists. Kilo fetches news only while you are signed in, and refetches after you sign in, sign out, or switch teams. | |
| The command palette has **Hide news** and **Show news** on the home screen, and the choice persists. Kilo fetches news once at startup when you are signed in; restart to refresh it. |
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
| With catalog mode on: | ||
|
|
||
| - The key serves catalog model IDs such as `moonshotai/kimi-k2.6`, and its supported models list shows those IDs. The provider-prefixed IDs are no longer served by the key. | ||
| - [Auto Model](/docs/code-with-ai/agents/auto-model) and custom routers can route matching catalog models through the key. For the catalog models it serves, the key is used ahead of a ChatGPT connection and your other BYOK keys. |
Contributor
There was a problem hiding this comment.
[WARNING]: Catalog-mode precedence contradicts the rules above
Line 149 says "Eligible requests use a connected ChatGPT subscription first" and line 152 says the BYOK key is used only when the request is not served by a connected subscription like ChatGPT. This bullet says a catalog-mode key is used ahead of a ChatGPT connection for the catalog models it serves. Readers cannot tell which rule wins; qualify the earlier rule (for example, note the catalog-mode exception) or move the precedence statement up next to it.
|
|
||
| By default, a provider key serves models under that provider's own IDs. You can switch a key to serve Kilo catalog model IDs instead by turning on **Use Kilo catalog model IDs** when you add or edit the key. | ||
|
|
||
| Catalog mode is off by default for new and existing keys. It is offered only for providers that map at least one model to a catalog ID, and it is not available for Vercel BYOK keys or for the OpenRouter and Vercel AI Gateway keys. |
Contributor
There was a problem hiding this comment.
[SUGGESTION]: "Vercel BYOK keys" is not defined on this page
The supported-provider lists add "Vercel AI Gateway" under Gateway keys, and no plain "Vercel" provider is listed, so it is unclear what the separate "Vercel BYOK keys" exclusion means next to the "Vercel AI Gateway keys" exclusion in the same sentence. Name the provider exactly as it appears on the BYOK page, or merge the two exclusions if they refer to the same thing.
| - Cache hits are billed at a discounted rate compared to regular input tokens. | ||
| - Requests using **Auto Free** models are billed at $0 on Kilo's side. | ||
| - **BYOK (Bring Your Own Key)** requests are billed at $0 on Kilo's side — you pay the provider directly. | ||
| - **BYOK (Bring Your Own Key)** requests are not charged for inference on Kilo's side — you pay the provider directly. Kilo still charges for the gateway-side costs it incurs on the request, such as server tools, plugins, and PDF parsing. |
Contributor
There was a problem hiding this comment.
[WARNING]: Other docs still state BYOK costs are $0 on Kilo's side
This change correctly adds that Kilo charges gateway-side costs, but packages/kilo-docs/pages/gateway/usage-and-billing.md:31 ("the cost is set to $0 on Kilo's side") and packages/kilo-docs/pages/gateway/authentication.md:113 ("Usage is tracked but not billed to your Kilo balance (cost is set to $0)") were not updated. Those pages now contradict this one and could mislead users into not expecting a charge; update them in the same PR.
github-actions
Bot
changed the title
github-actions
Bot
changed the title
| ### Routing modes | ||
|
|
||
| New entries are benchmarked on demand before they can serve traffic. Each entry shows a status: | ||
| Account owners choose a routing mode in the Kilo web app. The mode decides how each request is matched to a candidate from the pool, and it applies to the platform Efficient and Frontier tiers and to each custom auto router. |
Contributor
There was a problem hiding this comment.
[SUGGESTION]: Cheapest is not in the CLI's custom-router mode schema
This paragraph says the routing mode applies to each custom auto router, but the CLI validates a router's mode with AutoRoutingModeSchema = z.enum(["cost_per_accuracy", "best_accuracy"]) (packages/kilo-gateway/src/api/custom-router.ts:161) and kilo auto router list prints that value. If the web app can save a custom router as Cheapest, the CLI will fail to parse the router summary until the enum is extended; otherwise, scope this sentence and the Cheapest row to the platform tiers.
|
|
||
| The chat UI uses a 13px font by default. Change it from 10 to 24 under **Settings → Display**, and the extension applies the size to every open Kilo webview. In VS Code settings, the same value is the `kilo-code.new.fontSize` setting. | ||
|
|
||
| **Username** under the same tab sets the name shown on your messages in conversations. It is stored as `username` in `kilo.jsonc`. |
Contributor
There was a problem hiding this comment.
[SUGGESTION]: Username is not shown on messages in the VS Code chat
This section is in the VSCode tab, but the webview never renders username: the only consumer of the config value in this checkout is local server basic auth (packages/opencode/src/server/auth.ts:31), and VscodeUserMessage/UserMessageDisplay render no author name. Either scope the sentence to conversations that do show it (such as the CLI) or drop the display claim.
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-31
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-30T07:01:39.938Z→2026-10-31T07:01:29.877ZSurface:
cliother(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/opencode/,packages/tui/,packages/server/,packages/sdk/,packages/plugin/packages/kilo-docs/pages/getting-started/,packages/kilo-docs/pages/code-with-ai/,packages/kilo-docs/pages/customize/,packages/kilo-docs/pages/automate/other:packages/kilo-docs/pages/community/,packages/kilo-docs/pages/contributing/,packages/kilo-docs/LEARNINGS.md,docs/cliare ranked from git history overpackages/opencode/,packages/tui/,packages/server/,packages/sdk/,packages/plugin/(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
None.
Considered, no docs change needed
permissionsarray with renamedshell/subagentactions and adds packages/kilo-vscode/test/permission-rules.test.ts, but the current tree's Auto-Approve UI uses the documentedpermissionobject withbash/taskand permission-utils.ts has different signatures; settings/tabs.ts and that test path are absent. Current behavior is already documented in pages/getting-started/settings/auto-approving-actions.md.(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-31.