docs: add Cost Controls and Usage Safeguards page - #11715
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (1 file)
Previous Review Summaries (3 snapshots, latest commit 5761f8b)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 5761f8b)Status: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Previous review (commit a2af9a9)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (1 file)
Previous review (commit 10fcd8b)Status: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.4-20260305 · Input: 58.1K · Output: 6.7K · Cached: 244.5K Review guidance: REVIEW.md from base branch |
Updated rate limit information for free models and clarified configuration locations. Removed outdated sections on Auto Models and Enterprise features.
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Removed references to 'kilo-auto/free' model in configuration and updated comments accordingly.
| The snippet below is a ready-to-copy `kilo.jsonc` that turns on every available cost-control knob at its most restrictive setting. Drop it into your project root (or your global `~/.config/kilo/kilo.jsonc`) and adjust individual values upward as you get comfortable with how each one behaves. | ||
|
|
||
| {% callout type="tip" %} | ||
| This configuration uses only `kilo-auto/efficient`. |
There was a problem hiding this comment.
WARNING: The example no longer matches its own model-usage description
This callout now says the starter config uses only kilo-auto/efficient, but the snippet still sets agent.explore, agent.compaction, agent.title, and agent.summary to kilo-auto/free. That leaves the copy-paste example self-contradictory unless either the callout text or those remaining agent entries are updated.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
…d-usage-safeguards docs: add Cost Controls and Usage Safeguards page
3 participants
Summary
getting-started/cost-controls-and-usage-safeguardscovering all currently available controls for preventing runaway usage, reducing token consumption, choosing models by task type, and governing spend at the org level.kilo.jsoncsnippet covering every available cost-control field set to its most restrictive value, using onlykilo-auto/efficientandkilo-auto/freetiers.What's in the page
The page complements the existing Cost Efficiency & Model Selection page by going deeper on safeguard configuration rather than repeating the Auto Model tier overview or per-request cost math.
Sections:
@filetargeting, permission deny rules for build/generated dirs, compaction config, max output tokens, project instructions, MCP server management, and prompt cachingkilo.jsonc, org-level restrictionskilo.jsonccoveringmodel,small_model,subagent_model, per-agentmodelandsteps, allcompactionsub-fields (auto,threshold_percent,prune,tail_turns,preserve_recent_tokens,reserved),tool_outputtruncation thresholds, all relevantpermissionentries (bash,edit,task,webfetch,websearch,doom_loop), andshare— every field verified against the live config schema and set to its most restrictive optionAll content is based on features verified in the existing docs and codebase. No planned or speculative features are described.
Built for Lígia Zanchet by Kilo for Slack