diff --git a/packages/kilo-docs/pages/automate/agent-manager.md b/packages/kilo-docs/pages/automate/agent-manager.md index b4517d4ae8f1..f35b3e96fddc 100644 --- a/packages/kilo-docs/pages/automate/agent-manager.md +++ b/packages/kilo-docs/pages/automate/agent-manager.md @@ -369,6 +369,8 @@ The tool supports two modes: | `worktree` | Creates one Agent Manager git worktree and session per task. Each task gets an isolated checkout, branch, directory, and terminal. | | `local` | Creates Agent Manager sessions in the current workspace without git worktree isolation. You can also target an existing managed worktree with its `worktreeID`. | +In `worktree` mode, set a task's `baseBranch` to start its new worktree from a specific existing branch, like the base branch in the New Worktree dialog. Use the branch name without a remote prefix, such as `main` or `release/1.0`. When omitted, the worktree starts from the configured default base branch, or the repository default branch when no default is configured. A task `baseBranch` cannot be combined with `local` mode or `worktreeID`. + Starting another session in an existing worktree reuses its files and branch without rerunning setup. Coordinate edits between sessions sharing that checkout. Each request can start up to 20 tasks. Sessions started with a prompt inherit the current turn's model and reasoning effort unless you explicitly request a different selection. Sessions created without a prompt use the normal defaults. Ask for independent sessions for separate tasks, or alternate versions of the same task to compare approaches. diff --git a/packages/kilo-docs/pages/automate/code-reviews/github.md b/packages/kilo-docs/pages/automate/code-reviews/github.md index afdd9ad3d22f..b4af76ee30c4 100644 --- a/packages/kilo-docs/pages/automate/code-reviews/github.md +++ b/packages/kilo-docs/pages/automate/code-reviews/github.md @@ -97,6 +97,7 @@ Turn automated reviews on or off for an individual repository to override the in - Check the Code Reviews page for error details on specific reviews - Ensure you have sufficient Kilo Code credits +- A review on a paid model does not start when your balance is below the Cloud Agent minimum. Add credits or select a free or BYOK model, then push a new commit to run the review again. - Very large PRs may time out — consider splitting the change into smaller PRs ### The GitHub App is missing permissions diff --git a/packages/kilo-docs/pages/automate/code-reviews/gitlab.md b/packages/kilo-docs/pages/automate/code-reviews/gitlab.md index 1d6e1b52ef17..42326dd243b0 100644 --- a/packages/kilo-docs/pages/automate/code-reviews/gitlab.md +++ b/packages/kilo-docs/pages/automate/code-reviews/gitlab.md @@ -119,6 +119,7 @@ You need **Maintainer role** on the GitLab project. Both webhook creation and bo - Check the Code Reviews page for error details - Ensure you have sufficient Kilo Code credits +- A review on a paid model does not start when your balance is below the Cloud Agent minimum. Add credits or select a free or BYOK model, then push a new commit to run the review again. - Large MRs may time out — consider splitting the change into smaller MRs ### No projects listed after connecting diff --git a/packages/kilo-docs/pages/automate/code-reviews/overview.md b/packages/kilo-docs/pages/automate/code-reviews/overview.md index 5476eb4921e5..4aceda6a1bc9 100644 --- a/packages/kilo-docs/pages/automate/code-reviews/overview.md +++ b/packages/kilo-docs/pages/automate/code-reviews/overview.md @@ -37,6 +37,12 @@ Before enabling Code Reviews: - [Kilo Discord](https://discord.gg/hZnd57qN) - **Kilo Code credits are still used** when the agent performs model reasoning during a review. +### Credit requirement for paid models + +A review on a paid model starts only when the owning account's available balance covers the Cloud Agent minimum balance, so a review is never dispatched when its model usage cannot be paid for. If the balance is too low, the review fails before any model runs: Kilo posts a billing notice on the pull or merge request, leaves the review without comments, and marks the platform check as action required (GitHub) or the commit status as failed (GitLab). + +Reviews on free models, on models you connect with your own key (BYOK), and on organizations sponsored through Kilo's OSS program skip this check. Every model the review runs is evaluated. + ## Concurrent reviews Cloud Code Reviews limit how many reviews one owner can run at the same time. Reviews past that limit wait, then start when a slot opens. Local `/review` commands do not count toward this limit. diff --git a/packages/kilo-docs/pages/code-with-ai/agents/auto-model.md b/packages/kilo-docs/pages/code-with-ai/agents/auto-model.md index d09392976dcc..eb7d7f629ead 100644 --- a/packages/kilo-docs/pages/code-with-ai/agents/auto-model.md +++ b/packages/kilo-docs/pages/code-with-ai/agents/auto-model.md @@ -41,29 +41,23 @@ The underlying models behind each Auto Model tier are updated server-side as bet You get lean costs on routine work and stronger models when the work demands it — with no manual switching. -### Custom Efficient pools +### Platform pools -You can constrain `kilo-auto/efficient` to the exact models you trust by configuring an **Efficient model pool** on the **Auto routing** card: +Kilo selects the model pool for `kilo-auto/efficient` and `kilo-auto/frontier`; they are not configurable per owner. You can still choose your account's platform routing mode, and organization model policy continues to filter which models its members can route to. -- **Personal** — your [profile page](https://app.kilo.ai/profile) -- **Organization** — your organization's **Providers & Models** page. Owners and billing managers can edit; members see a read-only view. +To route across the exact models you trust — including client models the gateway cannot reach — create a [custom auto router](#custom-auto-routers). -A pool holds 1–10 exact model and thinking-variant pairs. Variants stay distinct, so the same model with different thinking variants (for example `max` and `xhigh`) counts as separate entries. Leave the pool empty to inherit: an organization without a pool uses each member's personal pool, and a member without a personal pool uses the platform pool. +### Routing modes -New entries are benchmarked on demand before they can serve traffic. Each entry shows a status: +Account owners choose a routing mode in the Kilo web app. The mode decides how each request is matched to a candidate from the pool, and it applies to the platform Efficient and Frontier tiers and to each custom auto router. -| Status | Meaning | +| Mode | Behavior | |---|---| -| Benchmarking | The pair is being measured and is not used for routing yet | -| Ready | Proven accurate enough and eligible for routing | -| Failed | Benchmarking failed — retry the entry | -| Unavailable | The model or variant is no longer in your catalog — remove the entry | +| **Best accuracy** | Routes to the most accurate candidate that passes the router's filters. | +| **Cost per accuracy** | Balances cost against accuracy, preferring a cheaper candidate but tolerating small cost differences so it does not switch away from a solid incumbent for a marginal saving. | +| **Cheapest** | Routes to the lowest-cost candidate that still meets the router's accuracy threshold. A cost tie goes to the higher-accuracy candidate, and when no candidate meets the threshold it routes to the most accurate candidate instead. | -Routing decides only among ready entries. If no pool entry can serve a request, the request falls back to a fixed, cost-effective baseline model, so quality never drops below that baseline. - -{% callout type="note" %} -You can benchmark up to 10 new or retried pairs per owner per rolling 24 hours. Entries that are already ready or benchmarking don't count against this limit. -{% /callout %} +Cheapest reuses the same deny, capability, and active filters as the other modes, along with the low-confidence override that falls back to the most accurate model. Once Cheapest selects a model, that model must keep meeting the router's strict accuracy threshold to stay selected; the small-cost-difference tolerance applies only to Cost per accuracy. Cheapest keeps the model variant it picked. {% callout type="warning" title="Data handling for Auto Free" %} Auto Free may route your requests to providers that log prompts and outputs and use them to improve their services. Do not submit personal or confidential data when using Auto Free. In particular, it may route to NVIDIA's free endpoints. @@ -71,6 +65,19 @@ Auto Free may route your requests to providers that log prompts and outputs and For NVIDIA free endpoints (Super/Ultra/etc): Trial use only - do not submit personal or confidential data. Your use is logged for security purposes and to improve NVIDIA products and services. The logged session data for improvement purposes is not linked to your identity or any persistent identifier. For more information about our data processing practices, see our [Privacy Policy](https://www.nvidia.com/en-us/about-nvidia/privacy-policy/). By interacting with this endpoint, you consent to our collection, recording, and use of such information and the [NVIDIA API Trial Terms of Service](https://assets.ngc.nvidia.com/products/api-catalog/legal/NVIDIA%20API%20Trial%20Terms%20of%20Service.pdf). {% /callout %} +### Custom auto routers + +A custom auto router is your own routing pool under a `kilo-auto/custom/` model id. Create the router in the Kilo web editor, then register the models this machine can run so the CLI can serve it locally instead of always forwarding to the gateway: + +- `kilo auto router list` — list your custom routers, their entries, and each entry's eval status +- `kilo auto router add ` — register a model configured in this CLI as a router entry +- `kilo auto router remove ` — remove a client model entry +- `kilo auto eval ` — run the router's missing client evals locally in Docker + +When you select a custom router, Kilo ranks the entries this machine can serve, asks the routing service for a decision, and runs the chosen model through its local provider. See the [CLI command reference](/docs/code-with-ai/platforms/cli-reference#kilo-auto) for every command and option. + +An entry can link to a platform model so it reuses that model's platform benchmark instead of running a local client eval. Pass `--measured-as ` to `kilo auto router add`, accept the link the CLI suggests when it finds a matching platform model, or set it in the web editor, which suggests a link for each entry and lets you pick another model or clear it. The link applies to each variant whose name matches a measured platform variant; other variants still need a client eval, and linked variants are skipped by `kilo auto eval`. A linked entry serves the newest platform measurement for that model and is flagged stale when the measurement is older than the current benchmark engine or the model has left the catalog. Once stored, a link stays until you clear it in the web editor. + ## Benefits ### Cost Optimization diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md index ab17625f169c..ce4045a23474 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md @@ -39,6 +39,8 @@ kilo --help After installation, run `kilo` and use the `/connect` command to add your first provider credentials. This is the interactive way to configure API keys for model providers. +The dialog lists each provider with a short description — Kilo Gateway is marked **Recommended**. When the Kilo Gateway model list cannot load, its row shows a red `!` with the reason, such as credentials rejected, not signed in, no connection, or a provider error, so you can fix the connection before starting a session. + ## Opening Links Links in agent responses use terminal hyperlink metadata when the terminal supports it. Kilo also handles links inside the TUI, so mouse capture does not make supported HTTP(S) links inactive. Move the pointer over a link to see the hover underline, then click it to open the default browser. @@ -122,9 +124,12 @@ The `kilo console` command and its browser interface are deprecated and will be #### Provider Commands -| Command | Description | -|---|---| -| `/connect` | Connect/add a provider - entry point for new users to add API credentials | +| Command | Aliases | Description | +|---|---|---| +| `/connect` | - | Connect/add a provider - entry point for new users to add API credentials | +| `/usage` | `/plans`, `/quota` | Show plan and quota usage for your connected providers | + +`/usage` opens a **Plans & usage** dialog with one card per detected source: Kilo coding plan quotas, ChatGPT (Codex) rate limits, and MiniMax Token Plan quotas. Each card shows the plan, the usage windows with their percentage used, any reset time, and a **Manage** link when the provider offers one. Press `ctrl+r` to refresh. #### System Commands @@ -262,6 +267,26 @@ The `diff_open` and `session_move` TUI keybindings run the same actions and are } ``` +## Home Screen and Session Sidebar + +### Home screen news + +When you are signed in to Kilo Gateway, the CLI home screen shows the most recent unread Kilo news item, with a `(N new)` count when more than one item is unread. Select the banner to open the **News** dialog, which lists every unread item and its action links. Opening the dialog marks those items as read, and they stay hidden after a restart. Items that are not intended for the CLI are not shown. + +The command palette has **Hide news** and **Show news** on the home screen, and the choice persists. Kilo fetches news only while you are signed in, and refetches after you sign in, sign out, or switch teams. + +### Session sidebar + +The session sidebar shows Kilo panels alongside the built-in ones: + +- **Branch PR** — the pull request for the current branch, when `gh` is installed and the branch has one. +- **Token Usage** — input, output, reasoning, cache read, and cache write tokens, cache hit rate, generation speed, and cost for the whole session, including subagents. +- **Models** — one row per provider and model, with its step count and cost. Expand a row for its token breakdown. +- **Terminal Bench 2.0** — the completion score and cost per attempt for the current Kilo model. +- **Footer** — your Kilo balance, Kilo Pass usage (personal accounts), and the Kilo version. + +Select a panel heading to collapse or expand it. + ## Permissions Kilo Code uses the permission config to decide whether a given action should run automatically, prompt you, or be blocked. @@ -707,6 +732,21 @@ The CLI supports overriding config values with environment variables. The suppor - For `kilocode` provider: `KILOCODE_` (e.g., `KILOCODE_MODEL` → `kilocodeModel`) - For other providers: `KILO_` (e.g., `KILO_API_KEY` → `apiKey`) +## Self-Hosted Backends + +By default the CLI sends Kilo API traffic (sign-in, profile, defaults) to `https://api.kilo.ai` and [AI gateway](/docs/gateway) traffic (chat, model listing, embeddings, autocomplete, transcription) to `https://ai-gateway.kilo.ai/api/v1`. Point either at a different server with these environment variables — for example, to route gateway traffic through a self-hosted gateway for compliance, or a local backend during development. + +| Variable | Default | Controls | +|---|---|---| +| `KILO_API_URL` | `https://api.kilo.ai` | Kilo API traffic. When set on its own (without `KILO_AI_GATEWAY_URL`), gateway traffic also goes here, under `/api/gateway/v1`. | +| `KILO_AI_GATEWAY_URL` | `https://ai-gateway.kilo.ai/api/v1` | AI gateway traffic only. | + +Set `KILO_AI_GATEWAY_URL` to send only gateway traffic to another server while leaving sign-in and profile requests on the default: + +```bash +KILO_AI_GATEWAY_URL=https://gateway.example.com/api/v1 kilo +``` + ## Using the CLI in an Organization If you belong to a Kilo organization (Team or Enterprise), you can route CLI requests through that organization. The process differs slightly between interactive and non-interactive usage. diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/slack.md b/packages/kilo-docs/pages/code-with-ai/platforms/slack.md index 469b135b7fde..4e01241d2de5 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/slack.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/slack.md @@ -140,6 +140,12 @@ To make proper use of all of the Kilo Slack bot's capabilities, it's important t --- +## Organization Slack integrations + +When Slack is connected to an organization, the integration is managed by the organization. Only organization owners and admins can connect, re-install, or disconnect Slack, and only they can change its model. Members see the connection state, can test the connection, and see a note explaining who manages the integration. + +--- + ## Changing the Model You can customize which AI model Kilo uses for generating responses. diff --git a/packages/kilo-docs/pages/customize/custom-modes.md b/packages/kilo-docs/pages/customize/custom-modes.md index a6ce037cb06e..4559f0f6e430 100644 --- a/packages/kilo-docs/pages/customize/custom-modes.md +++ b/packages/kilo-docs/pages/customize/custom-modes.md @@ -67,7 +67,12 @@ Kilo will generate the agent definition and write it to `.kilo/agent/` in your p ### 2. Using the Settings UI -You can manage agents through the **Settings → Agent Behaviour → Agents** subtab in the extension. This lets you view, create, and edit agent configurations — including the agent's prompt, model, permissions, and other properties. +You can manage agents through the **Settings → Agent Behaviour → Agents** subtab in the extension. It lists every visible agent with badges for custom, subagent, hidden, disabled, and deprecated entries, and lets you: + +- Set the **Default Agent** used when a session starts. +- Create an agent and edit its prompt, model, permissions, temperature, steps, and visibility. +- Import an exported agent JSON file, or export an agent to reuse elsewhere. +- Remove a config-defined agent. Built-in agents keep their base definition and expose overrides only. ### 3. Markdown Files with YAML Frontmatter diff --git a/packages/kilo-docs/pages/getting-started/adding-credits.md b/packages/kilo-docs/pages/getting-started/adding-credits.md index 34878d8ea6cd..a6915c7b56ed 100644 --- a/packages/kilo-docs/pages/getting-started/adding-credits.md +++ b/packages/kilo-docs/pages/getting-started/adding-credits.md @@ -15,6 +15,12 @@ These options are available to purchase from your [personal profile page](https: You can also use subscriptions or credits you may have purchased directly with an AI provider by adding your keys on the [Bring your own Key (BYOK)](https://app.kilo.ai/byok) settings screen. For setup details and supported providers, see [AI Providers documentation](/docs/ai-providers). If your provider is not yet supported, you can also [directly connect your provider](/docs/getting-started/setup-authentication) in the extension and CLI. +## Changing your Kilo Pass plan + +If you already have a Kilo Pass, you can change plans, including upgrading to a higher tier such as Expert, from the Kilo Pass subscription settings on your [profile page](https://app.kilo.ai/profile). A plan change takes effect when your next billing period starts, and your current pass stays active until then. You can cancel a pending change before it takes effect. + +If your subscription is set to cancel at the end of the current period, resume it before changing plans. Plan selection is disabled while cancellation is pending, because the subscription would end instead of switching plans. Canceling a Kilo Pass also releases any scheduled plan change. + ## Transparent Pricing At Kilo Code, we believe in complete pricing transparency: diff --git a/packages/kilo-docs/pages/getting-started/byok.md b/packages/kilo-docs/pages/getting-started/byok.md index ae66e477f38d..90b4f8dbdea6 100644 --- a/packages/kilo-docs/pages/getting-started/byok.md +++ b/packages/kilo-docs/pages/getting-started/byok.md @@ -29,6 +29,7 @@ Use your provider API key to route matching models through your account: - Azure Foundry (experimental) - DeepSeek - Fireworks +- GMI Cloud - Google AI Studio - Inception - Minimax @@ -61,6 +62,15 @@ These providers offer coding-focused subscriptions or dedicated endpoints. Bring - Xiaomi Token Plan (Singapore) - Z.ai Coding Plan +### Gateway keys + +These keys route through a gateway that already serves the regular Kilo catalog models, so no separate model entries are needed. Save the gateway's own API key: + +- OpenRouter +- Vercel AI Gateway + +A gateway key serves the catalog models its gateway provides. If you save both keys, the Vercel AI Gateway key is used for the models it serves, and the OpenRouter key covers requests that Vercel cannot serve. + ## Connect a ChatGPT subscription Connect **OpenAI (ChatGPT subscription)** on the [BYOK page](https://app.kilo.ai/byok) to use your subscription allowance for supported OpenAI models through the Kilo Gateway. No OpenAI API key is needed. @@ -143,6 +153,36 @@ These rules apply to saved API keys. Eligible requests use a connected ChatGPT s - If the key is invalid, the request fails. It does not fall back to using Kilo's keys. - Subscription-based providers (such as the Z.ai Coding Plan or Kimi Code) only expose the models included in that plan. Select one of those models to route traffic through your subscription. +## Preview the routes a model uses + +When you have at least one saved key, a **Routing preview** appears below the key list on the [BYOK page](https://app.kilo.ai/byok) and in the organization BYOK settings. Pick a catalog model and an API kind (default: Chat Completions) to see the routes a request would try, in order, and why each one is used or skipped: + +1. Direct BYOK keys whose provider serves the model, tried in Kilo's provider order. A key is skipped when its upstream does not offer the selected API kind, when the key is disabled, or when it uses provider model IDs instead of catalog IDs. +2. Your [ChatGPT connection](#connect-a-chatgpt-subscription) for eligible OpenAI models over the Responses API. The step is conditional because the connection is personal and its state is encrypted, so the preview cannot confirm it is active. +3. Vercel BYOK inference-provider keys, sent together through Vercel AI Gateway. Disabled keys are listed as skipped. +4. Your Vercel AI Gateway and OpenRouter keys, skipped when the key is disabled, when a provider key is preferred, or when the gateway does not serve the model. +5. Kilo's own route, through Vercel AI Gateway or OpenRouter, paid with Kilo credits. + +Steps below the one that serves the request, including a conditional ChatGPT step, are shown as **Not tried**. When no catalog-mode key serves the model, the preview shows the unsupported-API failure instead. Organization model and provider policies still apply. Changing a key on the page refreshes the preview. + +The preview reads your key metadata only. It never decrypts a key or calls the provider. + +## Serve Kilo catalog model IDs (catalog mode) + +By default, a provider key serves models under that provider's own IDs. You can switch a key to serve Kilo catalog model IDs instead by turning on **Use Kilo catalog model IDs** when you add or edit the key. + +Catalog mode is off by default for new and existing keys. It is offered only for providers that map at least one model to a catalog ID, and it is not available for Vercel BYOK keys or for the OpenRouter and Vercel AI Gateway keys. + +With catalog mode on: + +- The key serves catalog model IDs such as `moonshotai/kimi-k2.6`, and its supported models list shows those IDs. The provider-prefixed IDs are no longer served by the key. +- [Auto Model](/docs/code-with-ai/agents/auto-model) and custom routers can route matching catalog models through the key. For the catalog models it serves, the key is used ahead of a ChatGPT connection and your other BYOK keys. +- Organization model restrictions apply to requests that use the key. Keys without catalog mode keep their provider-prefixed IDs and stay exempt from those restrictions. + +Saved favorites are not rewritten when you switch a key to catalog mode. A saved model that used the provider-prefixed ID fails with a message naming the catalog ID to use; select the catalog model instead. + +Personal key owners can change catalog mode. For organization keys, only organization owners and admins can. + ## Using BYOK in the Extensions and CLI - BYOK works with the Kilo Gateway provider. Users should ensure that is set as the active [provider](/docs/ai-providers). diff --git a/packages/kilo-docs/pages/getting-started/rate-limits-and-costs.md b/packages/kilo-docs/pages/getting-started/rate-limits-and-costs.md index b5e174cef35f..e50e1314e786 100644 --- a/packages/kilo-docs/pages/getting-started/rate-limits-and-costs.md +++ b/packages/kilo-docs/pages/getting-started/rate-limits-and-costs.md @@ -77,7 +77,7 @@ Kilo automatically applies prompt caching on supported providers. Repeated conte - Kilo calculates an estimated cost for each request based on configured pricing. This estimate is shown per-request in the chat history. - Cache hits are billed at a discounted rate compared to regular input tokens. - Requests using **Auto Free** models are billed at $0 on Kilo's side. -- **BYOK (Bring Your Own Key)** requests are billed at $0 on Kilo's side — you pay the provider directly. +- **BYOK (Bring Your Own Key)** requests are not charged for inference on Kilo's side — you pay the provider directly. Kilo still charges for the gateway-side costs it incurs on the request, such as server tools, plugins, and PDF parsing. For current pricing, visit [kilo.ai/models](https://kilo.ai/models). diff --git a/packages/kilo-docs/pages/getting-started/settings/auto-approving-actions.md b/packages/kilo-docs/pages/getting-started/settings/auto-approving-actions.md index 0111b97957e0..19db33496931 100644 --- a/packages/kilo-docs/pages/getting-started/settings/auto-approving-actions.md +++ b/packages/kilo-docs/pages/getting-started/settings/auto-approving-actions.md @@ -55,6 +55,7 @@ The Auto Approve tab lists the following tool-specific permissions. Some tools a | `todoread` / `todowrite` | Reading and updating the todo list | | `websearch` | Performing web searches | | `webfetch` | Fetching content from URLs | +| `browser_open` | Opening pages in the Integrated Browser preview | | `doom_loop` | Allowing the agent to continue after repeated failures | ## Runtime Permission Requests @@ -87,6 +88,7 @@ Most tools default to `"*": "allow"` for a smooth out-of-the-box experience. Not - **`.env` files** — reading `.env` files prompts for approval. Files matching `*.env.*` (e.g., `.env.local`, `.env.production`) also trigger an ask, while `*.env.example` is explicitly allowed. - **`external_directory`** — accessing files outside the project prompts for approval +- **`browser_open`** — opening a page in the Integrated Browser preview prompts for approval. Approve the current origin or all origins from the prompt, or set **Browser Open** to **Allow** in the Auto-Approve settings to allow every navigation without prompting. See [Browser previews](/docs/automate/agent-manager#browser-previews). - **`doom_loop`** — prompts when the agent enters a repeated failure cycle - **`edit` (JetBrains plugin only)** — file edits prompt for approval. This is a plugin default, not an environment override: set `permission.edit` in your global or project `kilo.jsonc`, or use **Settings → Tools → Kilo Code → Auto-Approve**, to change it. diff --git a/packages/kilo-docs/pages/getting-started/settings/index.md b/packages/kilo-docs/pages/getting-started/settings/index.md index c84a2546afd4..708870be9840 100644 --- a/packages/kilo-docs/pages/getting-started/settings/index.md +++ b/packages/kilo-docs/pages/getting-started/settings/index.md @@ -170,6 +170,12 @@ You can change both choices later: Display changes apply as a draft. Click **Save** to keep them or **Discard** to revert. +### Display font size and username + +The chat UI uses a 13px font by default. Change it from 10 to 24 under **Settings → Display**, and the extension applies the size to every open Kilo webview. In VS Code settings, the same value is the `kilo-code.new.fontSize` setting. + +**Username** under the same tab sets the name shown on your messages in conversations. It is stored as `username` in `kilo.jsonc`. + ### Markdown Diff Rendering Markdown files in Kilo diff viewers can be shown as rendered Markdown instead of a raw text diff. Use the eye/code toggle in a Markdown file header, or set `kilo-code.new.diff.renderMarkdown` to `true` to render Markdown files by default. @@ -187,6 +193,10 @@ You can export and import settings from the **About Kilo Code** tab in the Setti Config files are also plain-text and portable — you can copy `~/.config/kilo/kilo.jsonc` between machines directly. +### Reset all settings + +**About Kilo Code → Reset All Settings** resets the VS Code extension–specific settings to their default values after a confirmation. Settings shared with the CLI, such as agents and auto-approve rules, live in your `kilo.jsonc` config and are not reset. This is the way to clear extension settings that are stored in VS Code rather than in the config file. + {% /tab %} {% tab label="CLI" %} @@ -220,6 +230,16 @@ Settings are resolved through an 8-level precedence system (lowest to highest pr Higher-priority levels override lower ones. This allows organizations to enforce settings at the enterprise level while still letting individual developers customize their local environment. +Enterprise-managed configuration is read from the system location for your platform: + +| Platform | Location | +|---|---| +| Linux | `/etc/kilo/` | +| macOS | `/Library/Application Support/kilo/` | +| Windows | `%ProgramData%\kilo\` | + +Managed files accept `kilo.jsonc`, `kilo.json`, `opencode.jsonc`, and `opencode.json`. They load after user, project, and runtime settings and take the highest priority. On macOS, an `ai.opencode.managed` preferences profile deployed by MDM is applied last, after the managed directory. + ### Schema Auto-Injection When you create or open a `kilo.jsonc` file, the CLI automatically injects a `$schema` property pointing to the config JSON schema. This gives you **autocompletion and validation** in any editor that supports JSON Schema (VS Code, JetBrains, etc.).