docs/guides/understanding-configs.mdx
Every developer has unique needs when it comes to AI assistance. Some prefer the convenience of cloud-managed configurations, while others need the control and privacy of local setups. Continue offers both paths, and this guide will help you choose the right one for your workflow.
Continue provides two distinct ways to configure:
Think of Continue's configuration options like choosing between a managed service and self-hosting. Both get you to the same destination—powerful AI assistance in your IDE—but the journey and control level differ significantly.
Before we dive into the specifics, let's understand how to access your configuration:
new window icon for Hub configsgear icon for Local configsHub Configurations represent the "it just works" philosophy. When you sign in to Continue Mission Control, you gain access to a curated ecosystem of established configurations that sync seamlessly across all your development environments.
The Power of Simplicity
The journey from zero to AI-powered coding takes just four steps:
Pro tip: Hub configurations are perfect for teams. Create a custom config with your team's coding standards, preferred models, and context sources, then share it with a simple link.
All Hub config management happens through Mission Control. For detailed customization, see our guide on Editing a Config.
Local configuration puts you in the driver's seat. Using a config.yaml file, you have complete control over every aspect of your Continue experience with all configuration stored directly on your machine.
Complete Control and Privacy
config.yaml into git alongside your code, ensuring reproducible environmentsLocal configuration lives in a single YAML file in your home directory:
File Locations:
~/.continue/config.yaml%USERPROFILE%\.continue\config.yamlQuick Access Method:
config.yaml file opens in your editorWhen you edit your config.yaml, Continue provides intelligent autocomplete for all available options. Save the file, and Continue automatically reloads your configuration—no restart required.
The first time you use Continue, it generates a config.yaml with sensible defaults. From there, you can customize everything from model selection to context providers, slash commands, and more.
For the complete configuration reference, see our config.yaml documentation.
The decision between Hub and Local configs often comes down to your specific needs and constraints. Here's a framework to help you decide:
Value Convenience Over Control
Need Advanced Collaboration
Are Getting Started
Require Maximum Control
Have Privacy Requirements
Are a Power User
Here's a secret: you don't have to choose just one. Many developers use both approaches:
You can switch between them seamlessly using the configs selector in your IDE.
config.yaml like code—commit it, review changes, and maintain historyChanges Not Reflecting?
Config Not Available?
Config Not Loading?
Autocomplete Not Working?
Now that you understand both configuration approaches, you're ready to dive deeper:
Remember, the best configuration is the one that helps you code more effectively. Start simple, experiment freely, and gradually refine your setup as you discover what works best for your workflow.
Happy coding with Continue! 🚀