Merge pull request #8782 from continuedev/dallin/assistant-config-docs-updates

docs: update assistants -> configs stragglers

Author: sestinj

docs/customization/prompts.mdx

@@ -6,7 +6,7 @@ description: "These are the specialized instructions that shape how models respo
 - **Define interaction patterns** for specific tasks or frameworks
 - **Encode domain expertise** for particular technologies
 - **Ensure consistent guidance** aligned with organizational practices
-- **Can be shared and reused** across multiple assistants
+- **Can be shared and reused** across multiple configs
 - **Act as automated code reviewers** that ensure consistency across teams
 
 ![Prompts Overview](/images/customization/images/prompts-blocks-overview-17194d870840576f9a0dde548f2c70ec.png)

docs/customization/rules.mdx

@@ -20,7 +20,7 @@ Your agent detects rules and applies the specified rules while in [Agent](/ide-e
 <Columns cols={2}>
 <Card title="Local Rules (.continue/rules)" icon="folder">
 - Create files in `.continue/rules` folder
-- Automatically appear with Hub assistants
+- Automatically appear with Hub configs
 - Edit directly in your file system
 - Version controlled alongside your code
 - Best for project-specific rules (e.g., "remember to generate migrations after modifying the db")

docs/customize/deep-dives/rules.mdx

@@ -31,7 +31,7 @@ Continue supports two types of rules with different behaviors:
 <Columns cols={2}>
 <Card title="Local Rules" icon="folder">
 - **Location**: `.continue/rules` folder in your workspace
-- **Visibility**: Automatically visible when using Hub assistants
+- **Visibility**: Automatically visible when using Hub configs
 - **Creation**: Add rules button in VSCode or manual file creation
 - **File Management**: Creates actual `.md` files you can edit directly
 </Card>
@@ -53,7 +53,7 @@ When using Continue, rules are loaded in this order:
 4. **Global rules** (from `~/.continue/rules` folder)
 
 <Info>
-**TL;DR**: Local rules show up automatically when using Hub assistants. Hub rules show up automatically when referenced in your config.
+**TL;DR**: Local rules show up automatically when using Hub configs. Hub rules show up automatically when referenced in your config.
 </Info>
 
 ## Quick Start: How to Create Your First Rule File
@@ -228,7 +228,7 @@ globs: ["**/*.ts", "**/*.tsx"]
 
 **Solution**:
 - **Hub rules** only appear when referenced in your config.yaml using the `uses:` syntax
-- **Local rules** automatically appear when using Hub assistants
+- **Local rules** automatically appear when using Hub configs
 - There's currently no automatic bidirectional sync
 
 ### Issue: "Edit" Links Point to Wrong Location

docs/customize/model-providers/top-level/bedrock.mdx

@@ -90,8 +90,8 @@ You can also use an AWS `accessKeyId` and `secretAccessKey` for authentication i
       model: <MODEL_ID>
       env:
         region: us-east-1
-        accessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }} # can also enter key inline here for local assistants
-        secretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }} # can also enter key inline here for local assistants
+        accessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }} # can also enter key inline here for local configs
+        secretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }} # can also enter key inline here for local configs
       roles:
         - chat
   ```

docs/getting-started/extensions.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Understanding Configs"
-description: "Continue offers two ways to configure your AI assistants"
+description: "Continue offers two ways to configure your AI agents"
 ---
 
 This content has moved to our comprehensive guide: [Understanding Hub vs Local Configuration](/guides/understanding-configs)

docs/guides/dlt-mcp-continue-cookbook.mdx

@@ -444,7 +444,7 @@ After completing this guide, you have a complete **AI-powered data pipeline deve
     icon="newspaper"
     href="https://dlthub.com/blog/deep-dive-assistants-mcp-continue"
   >
-    Learn about AI assistants, MCP, and Continue integration
+    Learn about AI agents, MCP, and Continue integration
   </Card>
   <Card
     title="MCP Concepts"

docs/home.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Introduction"
-description: "Learn how Continue enables developers to embrace continuous AI, enabling them to build custom AI code assistants with open source VS Code and JetBrains extensions featuring chat, autocomplete, edit, and agent capabilities"
+description: "Learn how Continue enables developers to embrace continuous AI, enabling them to build custom AI code agents with open source VS Code and JetBrains extensions featuring chat, autocomplete, edit, and agent capabilities"
 ---
 
 ## What is Continue?
 
-**Continue enables developers to create, share, and use custom AI code assistants with our open source [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension) extensions and [hub of models, rules, prompts, docs, and other building blocks](https://hub.continue.dev)**
+**Continue enables developers to create, share, and use custom AI code agents with our open source [VS Code](https://marketplace.visualstudio.com/items?itemName=Continue.continue) and [JetBrains](https://plugins.jetbrains.com/plugin/22707-continue-extension) extensions and [hub of models, rules, prompts, docs, and other building blocks](https://hub.continue.dev)**
 
 ## Key Features
 

docs/mission-control/configs/intro.mdx

@@ -74,7 +74,7 @@ You can interact with configs in three main ways:
 
   <Step title="Explore existing configs">
 
-    Browse the [Continue Mission Control](https://hub.continue.dev/explore?type=assistants) to see what configs others have built
+    Browse the [Continue Mission Control](https://hub.continue.dev/explore?type=configs) to see what configs others have built
 
   </Step>
 

docs/mission-control/governance/org-permissions.mdx

@@ -3,8 +3,8 @@ title: "Organization Permissions"
 description: "Users can have the following roles within an organization:"
 ---
 
-1. Admins are users who can manage members, secrets, blocks, assistants, etc.
-2. Members are users who can use assistants, blocks, secrets, etc.
+1. Admins are users who can manage members, secrets, blocks, configs, etc.
+2. Members are users who can use configs, blocks, secrets, etc.
 
 **User permissions for each role depend on the pricing plan:**
 

docs/mission-control/secrets/secret-resolution.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Secret Resolution"
-description: "User or Org secrets should be used depending on how users want them to be shared within their organization and assistants."
+description: "User or Org secrets should be used depending on how users want them to be shared within their organization and configs."
 ---
 
 For individual users and [Solo](/hub/governance/pricing#solo) organizations, secret resolution is performed in the following order: