db8bed0357
This consolidation addresses CON-4476 by eliminating confusing duplicate documentation paths. ## Changes Made ### Structure Consolidation - Removed /docs/customization/ directory entirely - Kept /docs/customize/ as the single canonical path (it contains comprehensive content including deep-dives, model-providers, and model-roles) - Moved better overview content from /customization/overview.mdx to /customize/overview.mdx - Added new top-level pages to /customize/: models.mdx, mcp-tools.mdx, rules.mdx, prompts.mdx, settings.mdx ### Navigation Updates - Removed duplicate "Customization" tab from docs.json navigation - Updated "Customize" tab to include the new top-level pages - All customization content now appears in a single, well-organized tab ### Redirects - Added redirects from all /customization/* paths to /customize/* - Ensures backward compatibility for bookmarks and external links - Updated existing redirects that pointed to /customization/overview ### Link Updates - Updated 16+ internal documentation links from /customization/ to /customize/ - Updated image paths from /images/customization/ to /images/customize/ - Consolidated image directories (removed /docs/images/customization/) ## Reasoning for Content Decisions ### Why Keep /customize/ Over /customization/? 1. More concise - Shorter path is easier to type and remember 2. Complete structure - Already contained extensive subdirectories (deep-dives/, model-providers/, model-roles/) 3. Active development - Model provider docs and deep-dives are actively maintained here 4. Better organization - Clear hierarchy with specialized subdirectories ### Content Consolidation Strategy - Overview page: Used /customization/overview.mdx as base (clearer introduction and practical examples) - New pages: Brought over /customization/ files that provided good card-based overviews for models, rules, prompts, MCP, and settings - Deep-dives: Kept existing comprehensive /customize/deep-dives/ content (no overlap with /customization/) - Model providers: Kept existing /customize/model-providers/ (no equivalent in /customization/) - Model roles: Kept existing /customize/model-roles/ (no equivalent in /customization/) ### Deleted Content Justification All files from /docs/customization/ were either: 1. Duplicates with less comprehensive content than /customize/ equivalents 2. Moved to /customize/ to serve as helpful overview pages 3. No unique information lost - content was either redundant or merged ## Success Metrics Addressed - Zero duplicate documentation paths - All internal links functional (verified) - Clear single source of truth for customization - Backward compatibility via redirects Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev> Co-authored-by: Username <nate@continue.dev>
34 lines
1.5 KiB
Plaintext
34 lines
1.5 KiB
Plaintext
---
|
|
title: Intro to Roles
|
|
description: Apply model role
|
|
keywords: [apply, model, role]
|
|
sidebar_position: 0
|
|
sidebar_label: Introduction
|
|
---
|
|
|
|
Models in Continue can be configured to be used for various roles in the extension.
|
|
|
|
- [`chat`](./chat.mdx): Used for chat conversations in the extension sidebar
|
|
- [`autocomplete`](./autocomplete): Used for autocomplete code suggestions in the editor
|
|
- [`edit`](./edit.mdx): Used to generate code based on edit prompts
|
|
- [`apply`](./apply.mdx): Used to decide how to apply edits to a file
|
|
- [`embed`](./embeddings.mdx): Used to generate embeddings used for vector search (@Codebase and @Docs context providers)
|
|
- [`rerank`](./reranking.mdx): Used to rerank results from vector search
|
|
|
|
These roles can be specified for a `config.yaml` model block using `roles`. See the [YAML Specification](/reference#models) for more details.
|
|
|
|
<Info>
|
|
For recommendations on which models work best for each role, see our [comprehensive model recommendations](/customize/models#recommended-models).
|
|
</Info>
|
|
|
|
## Selecting model roles
|
|
|
|
You can control which of the models in your config for a given role will be currently used for that role. Above the main input, click the 3 dots and then the cube icon to expand the `Models` section. Then you can use the dropdowns to select an active model for each role.
|
|
|
|
|
|
|
|
<Info>
|
|
`roles` are not explicitly defined within `config.json` (deprecated) - they
|
|
are infered by the top level keys like `embeddingsProvider`
|
|
</Info>
|