docs: agent --> config

[TyDunn]

Continue Documentation Naming Convention Update Specification

Background

• We used to have a single configuration file called config.json
• When we moved to config.yaml, we decided to support multiple configuration files, which we called "Assistants"
• We later renamed these "Assistants" to "Agents"
• We recently created "Workflows", which are markdown files that are used to kick off scoped, async tasks
• Now we are reorganizing our terminology for better clarity and consistency

Goal

• Rename "Agents" (YAML configurations) → "Configs" (for Continue CLI and IDE extensions)
• Rename "Workflows" (Markdown files) → "Agents" (background tasks)
• Create a clear, consistent terminology across all documentation
• Ensure a seamless transition for existing users

New Naming Conventions

Core Concepts

• Prompt: Describes the task to be completed by the agent
• Rules: Describe the constraints, policies, etc. of the solution
• MCP tools: Retrieve information in real-time and/or take an action in the real world
• Models: Intelligence that follows the prompt and uses tools to automate a task within the rules
• Agent: A prompt and a model with optional rules and MCP tools (formerly "Workflows")
• Trigger: An event or point in time that kicks off a Continuous AI workflow
• Outcome: An artifact you create and/or a communication you send
• (Continuous AI) Workflows: Trigger + Agent + Outcome
• Config: The YAML configuration file for Continue IDE extensions and CLI (TUI mode) (formerly "Agents")

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[cubic-dev-ai]

27 issues found across 60 files

Prompt for AI agents (all 27 issues)

Understand the root cause of the following 27 issues and fix them.


<file name="docs/faqs.mdx">

<violation number="1" location="docs/faqs.mdx:53">
Singular &quot;config&quot; conflicts with the plural pronoun &quot;them&quot; introduced in the rename; adjust the noun or pronoun for grammatical clarity.</violation>
</file>

<file name="docs/guides/doc-writing-agent-cli.mdx">

<violation number="1" location="docs/guides/doc-writing-agent-cli.mdx:205">
The Continue CLI still reads configuration files via the --config flag; replacing it with --agent makes this workflow command unusable because the flag is unsupported. Please keep the docs command on --config.</violation>
</file>

<file name="docs/guides/sentry-mcp-error-monitoring.mdx">

<violation number="1" location="docs/guides/sentry-mcp-error-monitoring.mdx:144">
The Continue CLI does not support a `--agent` flag yet—this quick-start command will fail unless it stays on the supported `--config` flag.</violation>
</file>

<file name="docs/customization/models.mdx">

<violation number="1" location="docs/customization/models.mdx:36">
Please change the article before “config” from “an” to “a” for grammatical correctness across these list items so the documentation reads clearly.</violation>
</file>

<file name="docs/index.mdx">

<violation number="1" location="docs/index.mdx:4">
Please align the landing description with the new naming by referring to Hub content as configs instead of agents.</violation>
</file>

<file name="docs/home.mdx">

<violation number="1" location="docs/home.mdx:22">
The new Continue Hub description now references a single “MCP tool,” but the hub exposes multiple MCP tools. Please keep this plural to reflect the actual offering.</violation>
</file>

<file name="docs/hub/source-control.mdx">

<violation number="1" location="docs/hub/source-control.mdx:3">
The closing sentence in this description ends with &quot;reach out to us on .&quot;, so readers never learn which channel to use. Please finish or remove the dangling phrase so the call to action is clear.</violation>
</file>

<file name="docs/hub/configs/create-a-block.mdx">

<violation number="1" location="docs/hub/configs/create-a-block.mdx:7">
The new heading is truncated (`## How to Remix a `), leaving the section title incomplete and confusing for readers. Please finish the phrase to reflect the intended concept.</violation>
</file>

<file name="docs/customize/overview.mdx">

<violation number="1" location="docs/customize/overview.mdx:10">
This link points to /guides/understanding-configs, but that page does not exist, so the documentation link will break. Please keep the existing /guides/understanding-agents link until the new page is published.</violation>
</file>

<file name="docs/hub/configs/intro.mdx">

<violation number="1" location="docs/hub/configs/intro.mdx:10">
This front matter block is inserted mid-document, so it will render as raw text and horizontal rules instead of updating the page metadata. Please remove it or move these fields into the existing top-level front matter.</violation>

<violation number="2" location="docs/hub/configs/intro.mdx:15">
The product name is misspelled as &quot;Contiue&quot;—please correct it to &quot;Continue&quot; to avoid confusing readers.</violation>
</file>

<file name="docs/ide-extensions/quick-start.mdx">

<violation number="1" location="docs/ide-extensions/quick-start.mdx:311">
This changes the Hub vs local link to /guides/understanding-configs, but the documented guide still lives at /guides/understanding-agents, so the new URL 404s. Please keep the existing route until the target page actually exists.</violation>
</file>

<file name="docs/customization/settings.mdx">

<violation number="1" location="docs/customization/settings.mdx:75">
`/guides/understanding-configs` does not exist in this repo, so this new link will 404; keep pointing at the existing guide until the new page lands.</violation>
</file>

<file name="docs/guides/dlt-mcp-continue-cookbook.mdx">

<violation number="1" location="docs/guides/dlt-mcp-continue-cookbook.mdx:56">
The Continue CLI still expects `--config &lt;path&gt;` when loading a hub config. Updating this snippet (and the other occurrences in the guide) to `cn --agent dlthub/dlt-assistant` will make the quick-start command fail because `--agent` is not a recognized flag. Please keep using `--config` until the CLI adds the new alias.</violation>
</file>

<file name="docs/hub/introduction.mdx">

<violation number="1" location="docs/hub/introduction.mdx:3">
The new description is missing &quot;with&quot; before &quot;organization-level&quot;, so the sentence no longer reads correctly.</violation>

<violation number="2" location="docs/hub/introduction.mdx:12">
&quot;Constaints&quot; is a typo; it should be spelled &quot;constraints&quot;.</violation>

<violation number="3" location="docs/hub/introduction.mdx:14">
The new Agents link points to /hub/agents/intro, but that path does not exist in the docs, so the link will be broken.</violation>
</file>

<file name="docs/getting-started/extensions.mdx">

<violation number="1" location="docs/getting-started/extensions.mdx:6">
The new link points to `/guides/understanding-configs`, but that route doesn’t exist in the docs yet, so this change creates a broken link. Please keep the link aimed at the existing guide (or add the new page before switching the URL).</violation>
</file>

<file name="docs/guides/continue-docs-mcp-cookbook.mdx">

<violation number="1" location="docs/guides/continue-docs-mcp-cookbook.mdx:34">
`cn --agent continuedev/docs-mintlify` will fail because the CLI only accepts the `--config` flag; please keep using `cn --config continuedev/docs-mintlify`.</violation>

<violation number="2" location="docs/guides/continue-docs-mcp-cookbook.mdx:398">
`cn` does not support a `--agent` option here; switch back to `--config` so the workflow runs.</violation>
</file>

<file name="docs/guides/sanity-mcp-continue-cookbook.mdx">

<violation number="1" location="docs/guides/sanity-mcp-continue-cookbook.mdx:78">
`cn --agent` is not a recognized Continue CLI flag; these instructions should keep using `--config` so the command works.</violation>

<violation number="2" location="docs/guides/sanity-mcp-continue-cookbook.mdx:450">
Switch this back to `--config`; `--agent` is not a valid flag for the Continue CLI.</violation>

<violation number="3" location="docs/guides/sanity-mcp-continue-cookbook.mdx:476">
Use the documented `--config` flag here; `--agent` will make the CLI exit with an error.</violation>
</file>

<file name="docs/guides/posthog-github-continuous-ai.mdx">

<violation number="1" location="docs/guides/posthog-github-continuous-ai.mdx:140">
This command now uses the unsupported `--agent` flag; the Continue CLI only accepts `--config` for loading these YAML configs, so following the doc will fail.</violation>
</file>

<file name="docs/customize/deep-dives/configuration.mdx">

<violation number="1" location="docs/customize/deep-dives/configuration.mdx:14">
The link now points to ../../hub/configs/edit-a-config.md, but that file doesn’t exist, so the documentation link is broken.</violation>
</file>

<file name="docs/guides/chrome-devtools-mcp-performance.mdx">

<violation number="1" location="docs/guides/chrome-devtools-mcp-performance.mdx:71">
The CLI still requires `--config` to load this hub entry; switching to `--agent` documents a flag that does not exist and causes the command to fail.</violation>

<violation number="2" location="docs/guides/chrome-devtools-mcp-performance.mdx:441">
The GitHub Actions workflow must keep using `--config`; documenting `--agent` instructs a flag the CLI does not support, so the workflow would fail.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[sestinj]

🎉 This PR is included in version 1.28.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.25.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀