Repository navigation
docs: auto-sync cloud-web with merged PRs (through 2026-09-23) - #14219
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| Organizations can subscribe to [Kilo Pass](https://kilo.ai/pricing/kilo-pass) at the organization level, pooling the subscription's credit capacity across the team instead of each member holding a personal Kilo Pass. Personal Kilo Pass subscriptions stay separate and are not affected. | ||
|
|
||
| A 5% payment-processing fee applies to Kilo Pass purchases. The fee is charged separately and does not increase the credits the pass provides. |
There was a problem hiding this comment.
Thanks for adding the 5% fee note. Worth clarifying whether the fee applies to renewals as well as new purchases.
github-actions
Bot
changed the title
|
|
||
| Organizations can subscribe to [Kilo Pass](https://kilo.ai/pricing/kilo-pass) at the organization level, pooling the subscription's credit capacity across the team instead of each member holding a personal Kilo Pass. Personal Kilo Pass subscriptions stay separate and are not affected. | ||
|
|
||
| A 5% payment-processing fee applies to Kilo Pass purchases. The fee is charged separately and does not increase the credits the pass provides. |
There was a problem hiding this comment.
Does the fee apply to annual passes too, or only monthly? The docs are not clear.
github-actions
Bot
changed the title
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| # Billing | ||
|
|
||
| Kilo seats use a transparent, two-part billing system: a monthly subscription per seat, plus pay-as-you-go Kilo credits. Model inference is charged at provider rates with no markup. A separate 5% payment-processing fee applies when you purchase credits. | ||
| Kilo seats use a transparent, two-part billing system: a monthly subscription per seat, plus pay-as-you-go Kilo credits. Model inference is charged at provider rates with no markup. A separate 5% payment-processing fee applies when you purchase credits, including automatic top-ups, and to Kilo Pass purchases. |
There was a problem hiding this comment.
[SUGGESTION]: Awkward parallel construction in the fee sentence
The phrase "applies when you purchase credits, including automatic top-ups, and to Kilo Pass purchases" mixes a when clause with a to phrase, so the two things the fee applies to aren't parallel. Making both objects parallel reads more cleanly.
| Kilo seats use a transparent, two-part billing system: a monthly subscription per seat, plus pay-as-you-go Kilo credits. Model inference is charged at provider rates with no markup. A separate 5% payment-processing fee applies when you purchase credits, including automatic top-ups, and to Kilo Pass purchases. | |
| Kilo seats use a transparent, two-part billing system: a monthly subscription per seat, plus pay-as-you-go Kilo credits. Model inference is charged at provider rates with no markup. A separate 5% payment-processing fee applies to credit purchases (including automatic top-ups) and to Kilo Pass purchases. |
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)
Incremental review of Previous Review Summaries (3 snapshots, latest commit ca20a36)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit ca20a36)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 26c5de0)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Previous review (commit 52de5ef)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (2 files)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
| Web and mobile session screens track the session and the message on screen, so you can pick the same session up somewhere else. Use the **Copy link** action in the session header to copy a link to the current position, then open that link on another device to land on the same message. | ||
|
|
||
| - A link that points at an older message loads older history, up to a bounded number of pages, to reach it. | ||
| - A link whose recorded message can no longer be reached opens at the end of the transcript. |
There was a problem hiding this comment.
This wording is good. Could we point out older links may need a retry?
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
changed the title
|
|
||
| ## Spend Alerts | ||
|
|
||
| Owners can set spend alerts in the spend view, on the web or in the mobile app, to be notified when spending crosses a limit or when an hour runs far above the usual rate. Alerts go to the owner's authorized billing contacts by email or mobile push. See [Spend alerts](/docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts) for how to configure them. |
There was a problem hiding this comment.
WARNING: The #spend-alerts anchor does not exist on the target page
The linked page packages/kilo-docs/pages/getting-started/cost-controls-and-usage-safeguards.md has no Spend alerts heading (its spend-related sections are Spending limits and the Minimum balance alerts bullet under Shared credit pool and auto top-up). The link therefore drops the reader at the top of that page instead of the promised configuration steps. Either add a Spend alerts section to that page, or point the link at the section that actually covers configuring alerts.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
github-actions
Bot
changed the title
|
|
||
| ## Spend Alerts | ||
|
|
||
| ## Spend alerts |
There was a problem hiding this comment.
WARNING: This added heading duplicates the section above it and leaves both empty
Lines 116 and 118 are now two back-to-back headings with nothing between them: ## Spend Alerts followed by ## Spend alerts. Both slugify to the same #spend-alerts anchor, so the page ends up with an empty duplicated section. The change looks like it meant to sentence-case the heading, but instead it replaced the section's body paragraph (the text describing when alerts fire and the link to /docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts), which dropped the pointer to the configuration steps.
Suggest removing one of the two headings and restoring the body under it, e.g. keep ## Spend alerts followed by the original text Owners can set spend alerts in the spend view, on the web or in the mobile app, to be notified when spending crosses a limit or when an hour runs far above the usual rate. Alerts go to the owner's authorized billing contacts by email or mobile push. See [Spend alerts](/docs/getting-started/cost-controls-and-usage-safeguards#spend-alerts) for how to configure them.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
…s 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. - Apply the review's parallel-construction fix to the processing-fee sentence. - Use sentence case in the new billing heading.
ca20a36 to
993d5d1
Compare
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. The review's parallel-construction fix on the fee sentence is in, and the new billing heading uses sentence case. The duplicate back-to-back heading from the earlier push is fixed.
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-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/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-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
(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.