Repository navigation
docs: auto-sync cli with merged PRs (through 2026-10-25) - #15139
github-actions[bot] wants to merge 9 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (7 files)
Previous Review Summaries (3 snapshots, latest commit 6092102)Current summary above is authoritative. Previous snapshots are kept for context only. 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: 122.6K · Output: 28.5K · Cached: 3.7M Review guidance: REVIEW.md from base branch |
| - `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. |
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.
| 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. |
|
|
||
| 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. |
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).
| 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. |
Automated docs sync — 2026-10-25
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-24T07:03:19.791Z→2026-10-25T07:03:39.767ZSurface:
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
(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-25.