diff --git a/packages/kilo-docs/pages/collaborate/sessions-sharing.md b/packages/kilo-docs/pages/collaborate/sessions-sharing.md index 86c62f407aae..b575660b4104 100644 --- a/packages/kilo-docs/pages/collaborate/sessions-sharing.md +++ b/packages/kilo-docs/pages/collaborate/sessions-sharing.md @@ -27,6 +27,16 @@ This information lets Kilo show your recent sessions and continue right from the 1. Open Cloud Agents → Recent Sessions and select the session you want to resume. 2. The chat will load with your previous messages and context so the agent can keep going without re-explaining your task. +### Resume on another device + +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. +- A link to a session your signed-in account cannot see shows **Not found** or **Access denied** with a **Back to sessions** action. +- If you open the link while signed out, the recorded position is kept through sign-in. +- After you send a message or command from a resumed position, the transcript follows the new output. + ## Share a session (read‑only) You can share a session with anyone via a link. A shared page: diff --git a/packages/kilo-docs/pages/collaborate/teams/billing.md b/packages/kilo-docs/pages/collaborate/teams/billing.md index 39358ce6b09c..6096e8e8c1b7 100644 --- a/packages/kilo-docs/pages/collaborate/teams/billing.md +++ b/packages/kilo-docs/pages/collaborate/teams/billing.md @@ -5,7 +5,7 @@ description: "Manage billing and subscriptions for your team" # 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 to credit purchases (including automatic top-ups) and to Kilo Pass purchases. {% callout type="note" %} @@ -72,6 +72,8 @@ To fill empty seats or remove members ahead of seat deletion, see the [team mana 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 every Kilo Pass purchase, including recurring billing. The fee is charged separately and does not increase the credits the pass provides. + - **One pass per seat** — purchased capacity always matches your paid seat count and adjusts automatically as seats are added or removed. - **Pooled credits** — each service window's Kilo Pass credits are issued to the organization's pool rather than to individuals. - **Child organizations** — if your organization has direct child organizations, you can allocate part of the pooled capacity to each child. Anything not allocated stays with the parent organization. @@ -111,6 +113,10 @@ The minimum top-up amount is **$100.00**. Once saved, your initial top-up will be processed immediately to verify your payment method. +## 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. + ## Invoices Invoices for any payment on the Kilo Code platform, for seats or credits, will be available in the Invoices tab. diff --git a/packages/kilo-docs/pages/getting-started/cost-controls-and-usage-safeguards.md b/packages/kilo-docs/pages/getting-started/cost-controls-and-usage-safeguards.md index ec281b1cae66..98d627a1e830 100644 --- a/packages/kilo-docs/pages/getting-started/cost-controls-and-usage-safeguards.md +++ b/packages/kilo-docs/pages/getting-started/cost-controls-and-usage-safeguards.md @@ -54,6 +54,19 @@ Organization accounts can additionally configure **per-user daily spending limit **Where to configure:** Organization spending limits are managed in the organization dashboard at [app.kilo.ai](https://app.kilo.ai). Individual credit top-up is at Settings → Adding Credits. +### Spend alerts + +A scope can notify its billing contacts when usage crosses a limit or runs far above its usual rate. Every account has a personal scope, and every organization has its own scope; each scope keeps its own alert settings. + +Two rule kinds are available, and you can switch each one on or off on its own: + +- **Spending limit** — fires when spend in a rolling 24-hour, 7-day, or 30-day window crosses the limit you set. +- **Spend spike** — fires when one hour's spend runs a set multiple (1x to 50x) above the scope's usual rate, taken from the previous 14 days of hourly usage. The rule stays quiet until the scope has a day of history. + +Each rule can send by email to the scope's billing contacts and by push to a signed-in Kilo mobile app. Push needs the app installed and its **Spend alerts** notification category on; in the mobile app, spend alerts are their own category, so you can turn them off without silencing agent notifications. + +**Where to configure:** the spend view at [app.kilo.ai](https://app.kilo.ai), or the same view in the Kilo mobile app. For an organization, owners, admins, and billing managers can manage the alerts. + ### Free model rate limits Requests to free models (`kilo-auto/free` and other free-tier models) are rate-limited to **200 requests per hour**. If you exceed this, requests return HTTP 429 and you must wait before continuing.