Repository navigation
docs: auto-sync cloud-mobile with merged PRs (through 2026-09-23) - #14198
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
changed the title
github-actions
Bot
changed the title
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Incremental review of the latest sync commit ( Files Reviewed (1 file)
Previous Review Summaries (6 snapshots, latest commit 7561750)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 7561750)Status: 1 Issue Found | Recommendation: Address before merge Incremental review of the latest sync commit ( Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Previous review (commit c66a41e)Status: 1 Issue Found | Recommendation: Address before merge Incremental review of the latest sync commit ( Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Previous review (commit 2b1dcbb)Status: No Issues Found | Recommendation: Merge Incremental review of the latest sync commit ( Files Reviewed (1 file)
Previous review (commit 1564bb7)Status: No Issues Found | Recommendation: Merge Incremental review of the latest sync commit ( Files Reviewed (1 file)
Previous review (commit b556f91)Status: No Issues Found | Recommendation: Merge Incremental review of the latest sync commit ( Files Reviewed (1 file)
Previous review (commit 599df34)Status: No Issues Found | Recommendation: Merge This is a docs-only sync PR (single file, Files Reviewed (1 file)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
| - Review GitHub pull requests, GitLab merge requests, and Bitbucket pull requests end to end — diffs, checks, comments, and merging. | ||
| - Start a new session on a connected `kilo remote` CLI instance with the **Run on** picker. | ||
|
|
||
| ## App actions |
There was a problem hiding this comment.
This section reads well. Consider linking the Shortcuts documentation for the iOS actions so the mapping is obvious.
|
Thanks! The docs sync looks good to me. |
|
Thanks! The docs sync looks good to me. 🎉 |
github-actions
Bot
changed the title
| - Review GitHub pull requests, GitLab merge requests, and Bitbucket pull requests end to end — diffs, checks, comments, and merging. | ||
| - Start a new session on a connected `kilo remote` CLI instance with the **Run on** picker. | ||
|
|
||
| ## App actions |
There was a problem hiding this comment.
The App actions list reads well. Could each item link to the merged PR it documents, as the intro promises?
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}
|
|
||
| A failed **Approve** or **Reply** keeps its buttons and reads **Couldn't answer. Tap again to retry.** An action that can no longer be answered reads **This request is no longer waiting.** and drops its buttons. Button labels follow the app language. | ||
|
|
||
| [Spend alerts](/docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts) arrive as their own push category. You can turn them off on their own, and the choice stays in sync with the spend view. |
There was a problem hiding this comment.
SUGGESTION: Broken anchor — #spend-alerts does not resolve
pages/getting-started/cost-controls-and-usage-safeguards.md has no Spend alerts heading; the closest section is ### Spending limits (anchor #spending-limits), and a repo-wide search finds spend-alerts only here. The docs link check (lychee-action in .github/workflows/docs-check-links.yml) runs without --include-fragments, so CI will not catch this. Consider pointing the link at an existing section or adding the Spend alerts heading on that page.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| A failed **Approve** or **Reply** keeps its buttons and reads **Couldn't answer. Tap again to retry.** An action that can no longer be answered reads **This request is no longer waiting.** and drops its buttons. Button labels follow the app language. | ||
|
|
||
| [Spend alerts](/docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts) arrive as their own push category. You can turn them off on their own, and the choice stays in sync with the spend view. |
There was a problem hiding this comment.
bot: This link points to a missing #spend-alerts fragment. The linked cost-controls page has a Spending limits heading, but no Spend alerts heading, so following the link will not reach the described feature.
Suggested fix: Link to an existing relevant section (for example, #spending-limits) or add a Spend alerts heading and documentation on the target page, then point this link to that heading.
github-actions
Bot
changed the title
|
kwf-e10-read-comment |
1 similar comment
|
kwf-e10-read-comment |
…inks to The sync linked `/docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts`, but that page has no such heading, so the link dropped the reader at the top. - Document the two spend-alert rule kinds (spending limit and spend spike), the email and push channels, and where to configure them, so the anchor resolves.
iscekic
left a comment
iscekic
left a comment
There was a problem hiding this comment.
The #spend-alerts link now resolves: this PR adds the ### Spend alerts section to the cost-controls page that the link targets.
Automated docs sync — 2026-09-23
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-09-22T07:04:14.221Z→2026-09-23T07:04:26.845ZSurface:
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/kiloclaw/,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-09-23.