-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix: assistants -> configs -> agents #8808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
✅ Review Complete Code Review Summary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 9 files
…allin/configs-assistants-cleanup-7
|
✅ Review Complete Code Review Summary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 issues found across 9 files
Prompt for AI agents (all 5 issues)
Understand the root cause of the following 5 issues and fix them.
<file name="docs/guides/cli.mdx">
<violation number="1" location="docs/guides/cli.mdx:57">
Update the example to reference the new fallback slug `continuedev/default-config` so the documentation matches the CLI behavior.</violation>
</file>
<file name="extensions/cli/src/configLoader.ts">
<violation number="1" location="extensions/cli/src/configLoader.ts:190">
The warning still says “falling back to default agent,” even though the changed code now loads the default config, leading to misleading logs.</violation>
<violation number="2" location="extensions/cli/src/configLoader.ts:375">
The function now fetches `continuedev/default-config`, but the thrown error still claims the default agent failed, resulting in an inaccurate error message.</violation>
</file>
<file name="extensions/cli/vitest.setup.ts">
<violation number="1" location="extensions/cli/vitest.setup.ts:17">
The fetch mock now watches for `default-cli-config`, but the CLI still requests `continuedev/default-config`, so the fallback request is no longer stubbed and tests will hit the network instead of the mock.</violation>
</file>
<file name="extensions/cli/spec/config-loading.md">
<violation number="1" location="extensions/cli/spec/config-loading.md:40">
The spec now claims the CLI falls back to `continuedev/default-cli-config`, but the implementation continues to load `continuedev/default-config`, so the documentation is incorrect.</violation>
</file>
Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR
|
🎉 This PR is included in version 1.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.36.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
More cases of "assistants" -> "configs" and migrating configs to agents. I created https://hub.continue.dev/continuedev/tidy-up-markdown-agent to make this work
Summary by cubic
Standardized terminology by switching from “assistants” to “configs” and updating workflows to use “agents.” Also changed the default fallback slug from continuedev/default-agent to continuedev/default-cli-config across CLI, docs, specs, and tests for consistency.
Refactors
Migration
Written for commit 011fdc4. Summary will update automatically on new commits.