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 cloud-mobile with merged PRs (through 2026-10-27) - #15048
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/
Reviewers are ranked from Kilo-Org/cloud; the workflow needs a token with contents: read on that repository (repository secret CROSS_REPO_ACCESS_TOKEN, exposed to the upsert step as CLOUD_REPO_TOKEN).
How the two were computed: Reviewers for cloud-mobile are ranked from Kilo-Org/cloud git history over apps/mobile/ (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.
Already documented: pages/getting-started/adding-credits.md has a 'Changing your Kilo Pass plan' section covering upgrading to a higher tier (Expert), next-billing-period activation, and the pending-cancellation rule (resume before changing; canceling releases the scheduled change).
The change targets v2 paths that are not present in the current source tree (packages/kilo-plugin/src/gateway/opencode.ts, packages/kilo-cli/, packages/tui/src/component/dialog-integration.tsx, migration-tracking/, and the kilocode.gateway.opencode-free-tier plugin); none exist in this checkout, so the OpenCode free-tier hiding and v2 integration-dialog promotion cannot be verified.
The change hardens the internal cloud-agent-fork review-fix route by adding a confirmation gate and a per-actor rate limit. No product docs page documents starting a fix session from a review, so documenting only this step would produce orphaned content about an otherwise undocumented flow.
Paid-credit expiry is gated by the PAID_CREDIT_EXPIRATION_EFFECTIVE_AT policy setting and is off by default, so new purchases keep non-expiring legacy terms. Documenting one-year expiry now would document unreleased behavior.
The public custom 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.
BYOC Vercel compute enrollment is gated by the BYOC_VERCEL_IDS Worker environment variable (comma-separated user/organization IDs; empty disables enrollment), so it is only visible to allowlisted accounts, not the general audience the docs target.
Builds on #7609 and only changes what the credits page states once PAID_CREDIT_EXPIRATION_EFFECTIVE_AT is set; with the policy off the page still reads "Do not expire", so the user-visible credit terms are unchanged.
Custom auto routers are already documented: pages/code-with-ai/agents/auto-model.md (#custom-auto-routers) and pages/code-with-ai/platforms/cli-reference.md (#kilo-auto) describe kilo-auto/custom/<slug> routers and the kilo auto router list/add/remove and kilo auto eval commands 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 compute remains gated by the BYOC_VERCEL_IDS allowlist (the PR's own tests set BYOC_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.
Internal Cloud Agent discovery plumbing: cursor-paginated hosted-workspace RPC/list/get queries in session-ingest plus a workspaceId on root-session summaries. The PR adds no user-facing UI ("N/A - no visual changes"), and the docs do not describe the Cloud workspace catalog that Agent Manager consumes from it.
(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.
Details: Incremental review at c5fec26877 of the two paragraphs added since the previous review:
packages/kilo-docs/pages/code-with-ai/platforms/mobile.md:45 — the Start agent confirmation behavior (native alert with full prompt and repository, app foregrounded before the alert, Cancel returns a cancelled result). Reads correctly and does not contradict the App actions table, which describes invocation while the app is closed.
packages/kilo-docs/pages/code-with-ai/platforms/mobile.md:132 — organization-owned profiles being read-only for members. Consistent with the surrounding profile section.
No images or links were added, so the Markdoc image convention and the internal-link checks do not apply to the changed lines. The earlier anchor finding for /docs/code-with-ai/platforms/cloud-agent#choosing-where-sessions-run remains resolved: packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md:53 contains the ## Choosing where sessions run heading. No new inline comments were needed.
Details: Incremental review of the new ### MCP Apps views subsection at packages/kilo-docs/pages/code-with-ai/platforms/mobile.md:189-193. The heading nests correctly under ## Remote MCP servers, introduces no links or images, and its claims (sandboxed view limited to server-declared origins, no sampling/model-context/messages/downloads, tool calls restricted to discovered tools) are scoped to the mobile Quick Chat surface. No HTML <img> tags were added. The previously reported anchor finding is resolved: packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md:53 contains the ## Choosing where sessions run heading, so the /docs/code-with-ai/platforms/cloud-agent#choosing-where-sessions-run link at line 124 resolves; no new issue was raised for it.
Details: Incremental review of the new paragraph at packages/kilo-docs/pages/code-with-ai/platforms/mobile.md:120 (agent picker behavior for a computer run target). It is consistent with the CLI's remote agent catalog (packages/opencode/src/kilo-sessions/remote-agent-catalog.ts:6, which also names .kilo/agents as the project agent directory) and the rest of the page. No images or HTML <img> tags were added. The previous finding on line 124 is resolved: packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md:53 now contains the ## Choosing where sessions run heading, so the #choosing-where-sessions-run anchor resolves on this branch's merge result.
Details: This automated docs-sync PR adds four sections (forking from a message, remote MCP servers, web search in chat, on-device models) and one new link to mobile.md. The only defect found is the new anchor link on line 122. The other new internal link (/docs/automate/mcp/what-is-mcp) resolves to an existing page, heading hierarchy remains sequential, and no images or HTML <img> tags were introduced.
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-14)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-15)
Oct 15, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-15)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-16)
Oct 16, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-16)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-17)
Oct 17, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-17)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-20)
Oct 20, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-20)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-21)
Oct 21, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-21)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-22)
Oct 22, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-22)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-23)
Oct 23, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-23)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-24)
Oct 24, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-24)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-25)
Oct 25, 2026
github-actionsBot
changed the title
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-25)
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-27)
Oct 27, 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-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-mobileother(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/mobile/(Kilo-Org/cloud)packages/kilo-docs/pages/code-with-ai/platforms/mobile.mdother: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-mobileare ranked fromKilo-Org/cloudgit history overapps/mobile/(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.