fix broken referencelinks

bdougie · bdougie · commit 742c3df928e8 · 2025-07-02T12:20:14.000-07:00
diff --git a/docs/docs/advanced/00-overview.mdx b/docs/docs/advanced/00-overview.mdx
@@ -36,13 +36,13 @@ Understand how different models can be assigned specific roles in your developme
 
 Complete configuration reference and API documentation.
 
-[View Reference →](./reference)
+[View Reference →](/reference)
 
 ## Troubleshooting
 
 Solutions to common issues and debugging techniques.
 
-[Get Help →](./troubleshooting)
+[Get Help →](/troubleshooting)
 
 ---
 
diff --git a/docs/docs/advanced/context-integration/documentation.mdx b/docs/docs/advanced/context-integration/documentation.mdx
@@ -111,7 +111,7 @@ For bulk documentation site adds or edits, we recommend editing your global conf
   </TabItem>
 </Tabs>
 
-See [the config reference](../reference) for all documentation site configuration options.
+See [the config reference](/reference) for all documentation site configuration options.
 
 Indexing will re-sync upon saving the configuration file.
 
diff --git a/docs/docs/advanced/deep-dives/autocomplete.mdx b/docs/docs/advanced/deep-dives/autocomplete.mdx
@@ -98,7 +98,7 @@ The following settings can be configured for autocompletion in the IDE extension
 
 ### `config.json` Configuration
 
-The `config.json` configuration format (deprecated) offers further configuration options through `tabAutocompleteOptions`. See the [JSON Reference](../reference.mdx#tabautocompleteoptions) for more details.
+The `config.json` configuration format (deprecated) offers further configuration options through `tabAutocompleteOptions`. See the [JSON Reference](/reference#tabautocompleteoptions) for more details.
 
 ## FAQs
 
diff --git a/docs/docs/advanced/deep-dives/configuration.md b/docs/docs/advanced/deep-dives/configuration.md
@@ -26,15 +26,15 @@ To open this `config.yaml`, you need to open the assistants dropdown in the top-
 
 When editing this file, you can see the available options suggested as you type, or check the reference below. When you save a config file from the IDE, Continue will automatically refresh to take into account your changes. A config file is automatically created the first time you use Continue, and always automatically generated with default values if it doesn't exist.
 
-See the full reference for `config.yaml` [here](../../advanced/reference).
+See the full reference for `config.yaml` [here](/reference).
 
 ## Deprecated configuration methods
 
 :::info
 View the `config.json` migration guide [here](../yaml-migration.mdx)
 :::
 
-- [`config.json`](../reference.mdx) - The original configuration format which is stored in a file at the same location as `config.yaml`
+- [`config.json`](/reference) - The original configuration format which is stored in a file at the same location as `config.yaml`
 - [`.continuerc.json`](#continuercjson) - Workspace-level configuration
 - [`config.ts`](#configts) - Advanced configuration (probably unnecessary) - a TypeScript file in your home directory that can be used to programmatically modify (_merged_) the `config.json` schema:
   - `~/.continue/config.ts` (MacOS / Linux)
diff --git a/docs/docs/advanced/deep-dives/development-data.md b/docs/docs/advanced/deep-dives/development-data.md
@@ -16,6 +16,6 @@ You can also configure custom destinations for your data, including remote HTTP
 
 For hub assistants, data destinations are configured in `data` blocks. Visit the hub to [explore example data blocks](https://hub.continue.dev/explore/data) or [create your own](https://hub.continue.dev/new?type=block&blockType=data).
 
-See more details about adding `data` blocks to your configuration files in the [YAML specification](../../advanced/reference#data)
+See more details about adding `data` blocks to your configuration files in the [YAML specification](/reference#data)
 
 When sending development data to your own HTTP endpoint, it will receive an event JSON blob at the given `schema` version. You can view event names, schema versions, and fields [here in the source code](https://github.com/continuedev/continue/tree/main/packages/config-yaml/src/schemas/data).
diff --git a/docs/docs/advanced/deep-dives/docs.mdx b/docs/docs/advanced/deep-dives/docs.mdx
@@ -111,7 +111,7 @@ For bulk documentation site adds or edits, we recommend editing your global conf
   </TabItem>
 </Tabs>
 
-See [the config reference](../reference) for all documentation site configuration options.
+See [the config reference](/reference) for all documentation site configuration options.
 
 Indexing will re-sync upon saving the configuration file.
 
diff --git a/docs/docs/advanced/deep-dives/rules.mdx b/docs/docs/advanced/deep-dives/rules.mdx
@@ -176,7 +176,7 @@ Continue includes a simple default system message for [Chat](../../features/chat
 
 This can be viewed in the rules section of the toolbar (see above), or in the source code [here](https://github.com/continuedev/continue/blob/main/core/llm/constructMessages.ts#L4).
 
-Advanced users can override this system message for a specific model if needed by using `chatOptions.baseSystemMessage`. See the [`config.yaml` reference](../../advanced/reference#models).
+Advanced users can override this system message for a specific model if needed by using `chatOptions.baseSystemMessage`. See the [`config.yaml` reference](/reference#models).
 
 ### `.continuerules`
 
diff --git a/docs/docs/advanced/json-reference.md b/docs/docs/advanced/json-reference.md
@@ -5,7 +5,7 @@ keywords: [config, config_schema.json, json]
 ---
 
 :::info
-We recently introduced a new configuration format, `config.yaml`, to replace `config.json`. See the `config.yaml` reference and migration guide [here](./reference.md).
+We recently introduced a new configuration format, `config.yaml`, to replace `config.json`. See the `config.yaml` reference and migration guide [here](/reference).
 :::
 
 Below are details for each property that can be set in `config.json`. The config schema code is found in [`extensions/vscode/config_schema.json`](https://github.com/continuedev/continue/blob/main/extensions/vscode/config_schema.json).
@@ -14,7 +14,7 @@ Below are details for each property that can be set in `config.json`. The config
 
 ### `models`
 
-Your **chat** models are defined here, which are used for [Chat](./chat/how-to-use-it.md), [Edit](./edit/how-to-use-it.md) and [VS Code actions](./customize/deep-dives/vscode-actions.md).
+Your **chat** models are defined here, which are used for [Chat](/features/chat/how-it-works), [Edit](/features/edit/how-it-works) and [VS Code actions](/advanced/deep-dives/vscode-actions).
 
 Each model has specific configuration options tailored to its provider and functionality, which can be seen as suggestions while editing the json.
 
@@ -471,7 +471,7 @@ Several experimental config parameters are available, as described below:
   - `docstring`: Prompt for adding docstrings.
   - `fix`: Prompt for fixing code.
   - `optimize`: Prompt for optimizing code.
-- `modelContextProtocolServers`: See [Model Context Protocol](/customize/context-providers#model-context-protocol)
+- `modelContextProtocolServers`: See [Model Context Protocol](/customization/mcp-tools)
 
 Example
 
@@ -506,7 +506,7 @@ Example
 
 ### Fully deprecated settings
 
-Some deprecated `config.json` settings are no longer stored in config and have been moved to be editable through the [User Settings Page](./customize/deep-dives/settings.md). If found in `config.json`, they will be auto-migrated to User Settings and removed from `config.json`.
+Some deprecated `config.json` settings are no longer stored in config and have been moved to be editable through the [User Settings Page](/advanced/deep-dives/settings). If found in `config.json`, they will be auto-migrated to User Settings and removed from `config.json`.
 
 - `allowAnonymousTelemetry`: This value will be migrated to the safest merged value (`false` if either are `false`).
 - `promptPath`: This value will override during migration.
@@ -527,4 +527,4 @@ Some deprecated `config.json` settings are no longer stored in config and have b
   - `displayRawMarkdown`
   - `showChatScrollbar`
 
-  See [User Settings Page](./customize/deep-dives/settings.md) for more information about each option.
+  See [User Settings Page](/advanced/deep-dives/settings) for more information about each option.
diff --git a/docs/docs/advanced/model-roles/00-intro.mdx b/docs/docs/advanced/model-roles/00-intro.mdx
@@ -18,7 +18,7 @@ Models in Continue can be configured to be used for various roles in the extensi
 - [`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](../../advanced/reference#models) for more details.
+These roles can be specified for a `config.yaml` model block using `roles`. See the [YAML Specification](/reference#models) for more details.
 
 ## Selecting model roles
 
diff --git a/docs/docs/advanced/yaml-migration.mdx b/docs/docs/advanced/yaml-migration.mdx
@@ -11,8 +11,8 @@ Continue's YAML configuration format provides more readable, maintainable, consi
 See also
 
 - [Intro to YAML](https://yaml.org/)
-- [JSON Continue Config Reference](/advanced/reference)
-- [YAML Continue Config Reference](./reference.mdx)
+- [JSON Continue Config Reference](/reference)
+- [YAML Continue Config Reference](/reference)
 
 ## Create YAML file
 
@@ -38,9 +38,9 @@ Add all model configurations in `config.json`, including models in `models`, `ta
   - `inlineEdit` -> e.g. `roles: [chat, edit]`
   - `applyCodeBlock` -> e.g. `roles: [chat, apply]`
 
-Model-level `requestOptions` remain, with minor changes. See [YAML Continue Config Reference](./reference.mdx#models)
+Model-level `requestOptions` remain, with minor changes. See [YAML Continue Config Reference](/reference#models)
 
-Model-level `completionOptions` are replaced by `defaultCompletionOptions`, with minor changes. See [YAML Continue Config Reference](./reference.mdx#models)
+Model-level `completionOptions` are replaced by `defaultCompletionOptions`, with minor changes. See [YAML Continue Config Reference](/reference#models)
 
 <!-- TODO - ollama autodetect supported? -->
 
@@ -330,7 +330,7 @@ mcpServers:
 
 Some deprecated `config.json` settings are no longer stored in config and have been moved to be editable through the [User Settings Page](./deep-dives/settings.md) (Gear Icon). If found in `config.json`, they will be auto-migrated to User Settings and removed from `config.json`.
 
-See the [JSON Config Reference](./reference#fully-deprecated-settings) for more information on fully deprecated options.
+See the [JSON Config Reference](/reference#fully-deprecated-settings) for more information on fully deprecated options.
 
 The following top-level fields from `config.json` still work when using `config.json` but have been deprecated and don't have a YAML equivalent:
 
@@ -355,4 +355,4 @@ The following top-level fields from `config.json` have been deprecated. Most UI-
 
 ## New Configuration options
 
-The YAML configuration format offers new configuration options not available in the JSON format. See the [YAML Config Reference](./reference.mdx) for more information.
+The YAML configuration format offers new configuration options not available in the JSON format. See the [YAML Config Reference](/reference) for more information.
diff --git a/docs/docs/customization/mcp-tools.mdx b/docs/docs/customization/mcp-tools.mdx
@@ -18,7 +18,7 @@ Model Context Protocol servers provide specialized functionality:
 
 ## Learn More
 
-Learn more in the [MCP deep dive](../advanced/deep-dives/mcp.mdx), and view [`mcpServers`](../advanced/reference#mcpservers) in the YAML Reference for more details.
+Learn more in the [MCP deep dive](../advanced/deep-dives/mcp.mdx), and view [`mcpServers`](/reference#mcpservers) in the YAML Reference for more details.
 description: Model Context Protocol servers provide specialized functionality
 keywords: [mcp, blocks, model context protocol, integrations, tools]
 sidebar_position: 4
@@ -37,4 +37,4 @@ Model Context Protocol servers provide specialized functionality:
 
 ## Learn More
 
-Learn more in the [MCP deep dive](../advanced/deep-dives/mcp.mdx), and view [`mcpServers`](../advanced/reference#mcpservers) in the YAML Reference for more details.
+Learn more in the [MCP deep dive](../advanced/deep-dives/mcp.mdx), and view [`mcpServers`](/reference#mcpservers) in the YAML Reference for more details.
diff --git a/docs/docs/customization/models.mdx b/docs/docs/customization/models.mdx
@@ -21,4 +21,4 @@ These blocks form the foundation of the entire assistant experience, offering di
 
 Continue supports [many model providers](../advanced/model-providers/top-level/openai.mdx), including Anthropic, OpenAI, Gemini, Ollama, Amazon Bedrock, Azure, xAI, DeepSeek, and more. Models can have various roles like `chat`, `edit`, `apply`, `autocomplete`, `embed`, and `rerank`.
 
-Read more about roles [here](../advanced/model-roles/00-intro.mdx) and view [`models`](../advanced/reference#models) in the YAML Reference.
+Read more about roles [here](../advanced/model-roles/00-intro.mdx) and view [`models`](/reference#models) in the YAML Reference.
diff --git a/docs/docs/customization/prompts.mdx b/docs/docs/customization/prompts.mdx
@@ -18,4 +18,4 @@ These are the specialized instructions that shape how models respond:
 
 ## Learn More
 
-Prompt blocks have the same syntax as [prompt files](../advanced/deep-dives/prompts.md). The `config.yaml` spec for `prompts` can be found [here](../advanced/reference#prompts).
+Prompt blocks have the same syntax as [prompt files](../advanced/deep-dives/prompts.md). The `config.yaml` spec for `prompts` can be found [here](/reference#prompts).
diff --git a/docs/docs/customization/rules.mdx b/docs/docs/customization/rules.mdx
@@ -22,4 +22,4 @@ Your assistant detects rule blocks and applies the specified rules while in [Age
 
 ## Learn More
 
-Learn more in the [rules deep dive](../advanced/deep-dives/rules.mdx), and view [`rules`](../advanced/reference#rules) in the YAML Reference for more details.
+Learn more in the [rules deep dive](../advanced/deep-dives/rules.mdx), and view [`rules`](/reference#rules) in the YAML Reference for more details.
diff --git a/docs/docs/features/chat/how-it-works.mdx b/docs/docs/features/chat/how-it-works.mdx
@@ -50,7 +50,7 @@ Each code section in the AI response includes action buttons:
 
 ### Prompt Inspection
 
-View the exact prompt sent to the AI model in the [prompt logs](../../advanced/troubleshooting) for debugging and optimization.
+View the exact prompt sent to the AI model in the [prompt logs](/troubleshooting) for debugging and optimization.
 
 ### Context Providers
 
diff --git a/docs/docs/features/edit/how-it-works.mdx b/docs/docs/features/edit/how-it-works.mdx
@@ -10,4 +10,4 @@ The model response is then streamed directly back to the highlighted range in yo
 
 If you accept the diff, we remove the previously highlighted lines, and if you reject the diff, we remove the proposed changes.
 
-If you would like to view the exact prompt that is sent to the model during an edit, you can [find it in the prompt logs](../../advanced/troubleshooting#check-the-logs).
+If you would like to view the exact prompt that is sent to the model during an edit, you can [find it in the prompt logs](/troubleshooting#check-the-logs).
diff --git a/docs/docs/getting-started/install.md b/docs/docs/getting-started/install.md
@@ -22,7 +22,7 @@ Get Continue installed in your favorite IDE in just a few steps.
 ![move-to-right-sidebar](/img/move-to-right-sidebar.gif)
 
 :::info[Troubleshooting]
-If you have any problems, see the [troubleshooting guide](../advanced/troubleshooting) or ask for help in [our Discord](https://discord.gg/NWtdYexhMs)
+If you have any problems, see the [troubleshooting guide](/troubleshooting) or ask for help in [our Discord](https://discord.gg/NWtdYexhMs)
 :::
 
   </TabItem>
@@ -38,7 +38,7 @@ If you have any problems, see the [troubleshooting guide](../advanced/troublesho
 ![jetbrains-getting-started.png](/img/jetbrains-getting-started.png)
 
 :::info[Troubleshooting]
-If you have any problems, see the [troubleshooting guide](../advanced/troubleshooting) or ask for help in [our Discord](https://discord.com/invite/EfJEfdFnDQ)
+If you have any problems, see the [troubleshooting guide](/troubleshooting) or ask for help in [our Discord](https://discord.com/invite/EfJEfdFnDQ)
 :::
 
   </TabItem>
diff --git a/docs/docs/guides/getting-started.mdx b/docs/docs/guides/getting-started.mdx
@@ -99,7 +99,7 @@ Now that you're set up:
 
 ## Getting Help
 
-- Check our [troubleshooting guide](/advanced/troubleshooting)
+- Check our [troubleshooting guide](/troubleshooting)
 - Join our [Discord community](https://discord.gg/continue)
 - Browse [assistants in the hub](https://hub.continue.dev)
 
diff --git a/docs/docs/hub/assistants/create-an-assistant.md b/docs/docs/hub/assistants/create-an-assistant.md
@@ -32,6 +32,6 @@ Choose a name, slug, description, and icon for your assistant.
 
 The easiest way to create an assistant is to click "Create assistant" with the default configuration and then add / remove blocks using the sidebar.
 
-Alternatively, you can edit the assistant YAML directly before clicking "Create assistant". Refer to examples of assistants on [hub.continue.dev](https://hub.continue.dev/explore/assistants) and visit the [YAML Reference](../../advanced/reference#complete-yaml-config-example) docs for more details.
+Alternatively, you can edit the assistant YAML directly before clicking "Create assistant". Refer to examples of assistants on [hub.continue.dev](https://hub.continue.dev/explore/assistants) and visit the [YAML Reference](/reference#complete-yaml-config-example) docs for more details.
 
 ![New assistant YAML](/img/hub/assistant-create-yaml.png)
diff --git a/docs/docs/hub/blocks/00-intro.md b/docs/docs/hub/blocks/00-intro.md
@@ -9,4 +9,4 @@ keywords: [blocks, introduction, basics]
 
 Blocks are the components you use to build a custom AI code assistant. These include [models](./block-types.md#models), [rules](./block-types.md#rules), [context providers](./block-types.md#context), [prompts](./block-types.md#prompts), [docs](./block-types.md#docs), [data destinations](./block-types.md#data), and [MCP servers](./block-types.md#mcp-servers).
 
-Blocks follow the [`config.yaml`](../../advanced/reference) format. When combined with other blocks into a complete `config.yaml`, they form a custom AI code assistant.
+Blocks follow the [`config.yaml`](/reference) format. When combined with other blocks into a complete `config.yaml`, they form a custom AI code assistant.
diff --git a/docs/docs/hub/blocks/block-types.md b/docs/docs/hub/blocks/block-types.md
diff --git a/docs/docs/hub/blocks/create-a-block.md b/docs/docs/hub/blocks/create-a-block.md
diff --git a/docs/docs/hub/source-control.md b/docs/docs/hub/source-control.md
diff --git a/docs/docs/reference.mdx b/docs/docs/reference.mdx
