Repository navigation
docs: auto-sync cloud-mobile with merged PRs (through 2026-10-25) - #15048
github-actions[bot] wants to merge 11 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| For Cloud Agent sessions, choose a repository from GitHub, GitLab, or, for organizations, Bitbucket. The picker groups repositories by provider and includes **Recently used**. Each provider has its own connection and error messages, so a problem with one does not hide the others. | ||
|
|
||
| Cloud Agent sessions also offer a **Sandbox** field, which starts on the backend's default destination. Tap it to pick a sandbox type from a sheet that groups the types the backend offers by provider; the field then shows the choice, such as `Cloudflare · Shared`. While the options load, a field-sized skeleton holds the slot, and a failed load shows **Couldn't load sandbox options** with **Retry**. If a chosen type is no longer offered, the field shows why and offers **Use Default**, and you cannot start until you resolve it. Starting sends the type you picked, or the backend default when you pick nothing. Owners without sandbox selection see no Sandbox field. | ||
| Cloud Agent sessions also offer a **Sandbox** field, which starts on the backend's default destination. The owner's default sandbox and per-repository overrides are set in [Cloud Agent settings](/docs/code-with-ai/platforms/cloud-agent#choosing-where-sessions-run). Tap it to pick a sandbox type from a sheet that groups the types the backend offers by provider; the field then shows the choice, such as `Cloudflare · Shared`. While the options load, a field-sized skeleton holds the slot, and a failed load shows **Couldn't load sandbox options** with **Retry**. If a chosen type is no longer offered, the field shows why and offers **Use Default**, and you cannot start until you resolve it. Starting sends the type you picked, or the backend default when you pick nothing. Owners without sandbox selection see no Sandbox field. |
There was a problem hiding this comment.
WARNING: Broken internal anchor link
The link target /docs/code-with-ai/platforms/cloud-agent#choosing-where-sessions-run points to a heading that does not exist. cloud-agent.md has no "Choosing where sessions run" section (its headings are What Cloud Agents Enable, How to Use, How Cloud Agents Work, Worktrees and chats, etc.), and a search across the docs tree finds no choosing-where-sessions-run anchor anywhere. Users clicking this link land at the top of the Cloud Agent page instead of the sandbox settings.
Either point the link at the actual section that documents sandbox selection in cloud-agent.md, or add that section (with a matching heading) in this PR.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Details: Incremental review at
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 Previous Review Summaries (3 snapshots, latest commit 5d8f161)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 5d8f161)Status: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Details: Incremental review of the new Previous review (commit ab9bab7)Status: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Details: Incremental review of the new paragraph at Previous review (commit b2552d8)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (1 file)
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 Reviewed by deepseek-flash-latest · Input: 41.8K · Output: 2.9K · Cached: 310K 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
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
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:
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
(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.