Repository navigation
docs: auto-sync cloud-web with merged PRs (through 2026-10-27) - #14655
github-actions[bot] wants to merge 26 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)WARNING
SUGGESTION
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous Review Summaries (5 snapshots, latest commit 1c36bdc)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 1c36bdc)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit 73e30e0)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit f780e57)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit 93dbd3d)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Previous review (commit c8656e8)Status: No Issues Found | Recommendation: Merge Docs-only auto-sync PR (2 files). The new Files Reviewed (2 files)
Reviewed by deepseek-flash-latest · Input: 60.3K · Output: 9.4K · Cached: 738.3K Review guidance: REVIEW.md from base branch |
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
|
|
||
| ### Auto routing Tab | ||
|
|
||
| Holds your organization's Auto routing settings, including the Efficient model pool that constrains `kilo-auto/efficient` to specific model and thinking-variant pairs. Owners, admins, and billing managers can edit these settings; members see a read-only view. See [Custom Efficient pools](/docs/code-with-ai/agents/auto-model#custom-efficient-pools) for how the pool is benchmarked and routed. |
There was a problem hiding this comment.
WARNING: Permission claim conflicts with the dedicated Auto Model page
This says owners, admins, and billing managers can edit the Auto routing / Efficient model pool settings on the Providers & Models page, but the page dedicated to that same setting documents it as editable by owners and billing managers only: packages/kilo-docs/pages/code-with-ai/agents/auto-model.md:49 reads "Owners and billing managers can edit; members see a read-only view." Both describe the organization Efficient pool on the same page, so one of them is wrong. Please confirm the actual role set for the pool and align the two pages.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
|
|
||
| The same lifetime and new-message options apply when you share a cloud session from the web and when you share an authenticated session through MCP. Creating a replacement link disables the previous link for that session. Reopening the share dialog lets you copy the link that is already displayed instead of creating another one. | ||
|
|
||
| Unsharing a session, or creating a replacement link, disables the existing link. Links created before these options were available keep their original lifetime and message behavior; create a new link if you need a different duration or live updates. |
There was a problem hiding this comment.
SUGGESTION: Duplicates the previous paragraph
The previous paragraph already states "Creating a replacement link disables the previous link for that session." This sentence repeats it, so readers get the same rule twice back to back. Consider dropping the repeated clause here and keeping only the new information (unsharing, and how pre-existing links behave):
Unsharing a session disables its link. Links created before these options were available keep their original lifetime and message behavior; create a new link if you need a different duration or live updates.
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
Automated docs sync — 2026-10-27
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-25T07:03:39.767Z→2026-10-27T07:10:23.853ZSurface:
cloud-webother(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,otherapps/web/(Kilo-Org/cloud)packages/kilo-docs/pages/collaborate/other:packages/kilo-docs/pages/community/,packages/kilo-docs/pages/contributing/,packages/kilo-docs/LEARNINGS.md,docs/Kilo-Org/cloud; the workflow needs a token withcontents: readon that repository (repository secretCROSS_REPO_ACCESS_TOKEN, exposed to the upsert step asCLOUD_REPO_TOKEN).cloud-webare ranked fromKilo-Org/cloudgit history overapps/web/(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
publiccustom LLM field is configured by Kilo admins in the internal admin panel (apps/web/src/app/admin/custom-llms). Users have no configuration surface, and the public docs do not describe how Kilo curates its model catalog, so there is nothing user-facing to document.pages/code-with-ai/agents/auto-model.md(#custom-auto-routers) andpages/code-with-ai/platforms/cli-reference.md(#kilo-auto) describekilo-auto/custom/<slug>routers and thekilo auto router list/add/removeandkilo auto evalcommands with every option. The current tree (packages/opencode/src/kilocode/cli/cmd/auto.ts) matches what those pages say, so there is no new user-facing behavior to add.BYOC_VERCEL_IDSallowlist (the PR's own tests setBYOC_VERCEL_IDS: '*'), so it only refines picker behavior for enrolled accounts, not the general audience the docs target. The parent enrollment change (#8859) was skipped for the same reason, and the public docs already state that Vercel sandboxes are GitHub-only and that Platform default resolves to a named sandbox.(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-27.