Inline Completions#
Inline completions provide passive code suggestions as you type, using the same local model configured for the agent. Suggestions appear at the caret position and can be accepted or dismissed without leaving the keyboard.
Disabled by default. Enable at Settings → Llamatik Code → Autonomous Local Development → Enable inline completions.
How it works#
- You type in the editor and pause.
- After a configurable debounce delay (default 600 ms), the plugin collects the text before and after the caret (prefix and suffix).
- A fill-in-the-middle (FIM) prompt is sent to the local model.
- The model’s completion is inserted as an inline hint at the caret.
- Press Tab to accept, or keep typing to dismiss.
The request is cancelled automatically if you type again before the model responds — stale completions are never shown.
Privacy#
Completions are generated by the same local model used for the agent. No text is sent to any remote server. The context window for completions is intentionally small (default 1200 chars) to keep latency low.
Settings#
Settings live at Settings → Llamatik Code → Autonomous Local Development → Inline Completions.
| Setting | Description | Default |
|---|---|---|
| Enable inline completions | Master toggle | off |
| Debounce delay (ms) | Idle time before a request is sent | 600 ms |
| Max context chars | Characters of prefix + suffix sent to the model | 1200 |
| Max completion tokens | Maximum tokens in the generated completion | 64 |
Recommended values by hardware#
| Profile | Debounce | Max context | Max tokens |
|---|---|---|---|
| Low-end (< 8 GB RAM) | 1000 ms | 800 | 32 |
| Mid-range (8–16 GB) | 600 ms | 1200 | 64 |
| High-end (> 16 GB / GPU) | 300 ms | 2000 | 128 |
Supported models#
FIM completions work best with models that support the <fim_prefix> / <fim_suffix> / <fim_middle> token format, such as:
- Qwen2.5 Coder series
- DeepSeek Coder series
- CodeLlama (FIM variant)
- StarCoder2
For models that do not support FIM, the plugin falls back to a plain prefix-only prompt. Completions still work but may be less accurate for mid-line insertions.
Performance notes#
- Completions are generated on the same thread pool as the agent. Running a long agent task while inline completions are enabled may increase completion latency.
- If idle model unloading is enabled, the first completion after an idle period will be slower while the model reloads.
- Completions are limited to the current file only. Cross-file context is not included in the completion prompt.
Related#
- Autonomous Local Development — feature overview
- Settings Reference — full settings list