mirror of
https://github.com/Kilo-Org/kilocode.git
synced 2026-08-28 19:11:03 +08:00
docs(kilo-docs): update autocomplete docs for VSCode vs Legacy differences
Clarify that VSCode extension uses Codestral via Kilo Gateway exclusively, while preserving the multi-provider documentation for VSCode Legacy.
This commit is contained in:
@@ -12,7 +12,7 @@ Kilo Code's autocomplete feature provides intelligent code suggestions and compl
|
||||
|
||||
## How Autocomplete Works
|
||||
|
||||
The extension uses **Fill-in-the-Middle (FIM)** completion powered by Codestral (`mistralai/codestral-2508`). It analyzes the code before and after your cursor to generate contextually accurate inline suggestions.
|
||||
The extension uses **Fill-in-the-Middle (FIM)** completion powered by Codestral (`mistralai/codestral-2508`) via the **Kilo Gateway**. It analyzes the code before and after your cursor to generate contextually accurate inline suggestions.
|
||||
|
||||
## Triggering Options
|
||||
|
||||
@@ -28,6 +28,12 @@ Press `Cmd+L` (Mac) or `Ctrl+L` (Windows/Linux) to manually request a completion
|
||||
This keybinding requires `kilo-code.new.autocomplete.enableSmartInlineTaskKeybinding` to be enabled in VS Code settings. It is **disabled by default**.
|
||||
{% /callout %}
|
||||
|
||||
## Provider and Model
|
||||
|
||||
Autocomplete in the VSCode extension exclusively uses **Codestral** (`mistralai/codestral-2508`) routed through the **Kilo Gateway**. There is no option to select a different provider or model — the extension is designed to work specifically with Codestral, which is optimized for Fill-in-the-Middle (FIM) completions.
|
||||
|
||||
Requests are billed through your Kilo account. To use your own Mistral API key instead, see [Setting Up Mistral for Free Autocomplete](/docs/code-with-ai/features/autocomplete/mistral-setup).
|
||||
|
||||
## Status Bar
|
||||
|
||||
The extension displays an **autocomplete status indicator** in the VS Code status bar, including:
|
||||
@@ -130,11 +136,24 @@ If using Cursor, go to **Settings** > **Cursor Settings** > **Tab**, and toggle
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Balance speed and quality**: Faster models provide quicker suggestions but may be less accurate
|
||||
2. **Adjust trigger delay**: Find the sweet spot between responsiveness and avoiding too many API calls
|
||||
3. **Use Quick Task for complex changes**: It's designed for more substantial code modifications
|
||||
4. **Use Manual Autocomplete for precision**: When you need suggestions at specific moments
|
||||
5. **Configure providers wisely**: Consider using faster, cheaper models for autocomplete while keeping more powerful models for chat
|
||||
1. **Use Manual Autocomplete for precision**: When you need suggestions at specific moments, use the keyboard shortcut rather than relying on auto-trigger
|
||||
2. **Use chat for complex changes**: Chat is better suited for multi-file changes and substantial code modifications
|
||||
3. **Steer autocomplete with comments**: Write a comment describing what you want before triggering autocomplete, or type a function signature — autocomplete will fill in the implementation
|
||||
|
||||
{% tabs %}
|
||||
{% tab label="VSCode" %}
|
||||
|
||||
4. **Check the status bar**: The status bar shows autocomplete state and cost tracking — use it to monitor your usage
|
||||
|
||||
{% /tab %}
|
||||
{% tab label="VSCode (Legacy)" %}
|
||||
|
||||
4. **Balance speed and quality**: Faster models provide quicker suggestions but may be less accurate
|
||||
5. **Adjust trigger delay**: Find the sweet spot between responsiveness and avoiding too many API calls
|
||||
6. **Configure providers wisely**: Consider using faster, cheaper models for autocomplete while keeping more powerful models for chat
|
||||
|
||||
{% /tab %}
|
||||
{% /tabs %}
|
||||
|
||||
## Tips
|
||||
|
||||
@@ -142,17 +161,13 @@ If using Cursor, go to **Settings** > **Cursor Settings** > **Tab**, and toggle
|
||||
**When to use chat vs autocomplete:** Use chat for multi-file changes, refactoring, or when you need to explain intent. Use autocomplete for quick, localized edits where the context is already clear from surrounding code.
|
||||
{% /callout %}
|
||||
|
||||
{% callout type="tip" %}
|
||||
**Steer autocomplete with comments:** Write a comment describing what you want before triggering autocomplete, or type a function signature—autocomplete will fill in the implementation.
|
||||
{% /callout %}
|
||||
|
||||
{% callout type="tip" %}
|
||||
**Treat suggestions as drafts:** Accept autocomplete suggestions quickly, then refine. It's often faster to fix a 90% correct suggestion than to craft the perfect prompt.
|
||||
{% /callout %}
|
||||
|
||||
- Autocomplete works best with clear, well-structured code
|
||||
- Comments above functions help autocomplete understand intent
|
||||
- Variable and function names matter - descriptive names lead to better suggestions
|
||||
- Variable and function names matter — descriptive names lead to better suggestions
|
||||
|
||||
## Related Features
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
This guide walks you through setting up Mistral's Codestral model for free autocomplete in Kilo Code. Mistral offers a free tier that's perfect for getting started with AI-powered code completions.
|
||||
|
||||
{% tabs %}
|
||||
{% tab label="VS Code" %}
|
||||
{% tab label="VSCode" %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -74,7 +74,7 @@ Your Editor → Kilo Gateway (with your key) → Mistral
|
||||
- **Seeing charges on your Kilo balance?** If you haven't configured BYOK, autocomplete defaults to using your Kilo credits. Add your Codestral key via BYOK to route requests through your own Mistral account.
|
||||
|
||||
{% /tab %}
|
||||
{% tab label="VS Code Legacy" %}
|
||||
{% tab label="VSCode (Legacy)" %}
|
||||
|
||||
## Video Walkthrough
|
||||
|
||||
|
||||
Reference in New Issue
Block a user