Where Does Continue Store Config and Index Data?
Where the Continue coding assistant keeps config.yaml, workspaces, and index data on Windows, macOS, and Linux.
Last updated
Continue keeps a single .continue folder in your home directory across all three desktop OSes. The file that matters most is config.yaml at its root, which declares models, roles, and context providers.
Everything else in the folder is working state: indexed workspaces, retrieved docs, and logs. That split makes troubleshooting easy. Config problems mean editing one YAML file, while weird completions usually mean wiping a workspace cache. Hub users get models synced separately, so a local backup still matters for offline work.
Where Continue stores this, by platform
~/.continue
config.yaml (or config.json) sits at the root; edit it directly for model changes. The workspaces/ subdirectory holds one indexed cache per project. Hub users keep an extra auth file here, so exclude it from backups you share.
~/.continue
Same layout as macOS. JetBrains and VS Code installs share this folder, so settings carry across editors on the same machine. Logs beside the config help when the sidebar shows a blank model list.
%USERPROFILE%\.continue
Paste %USERPROFILE%\.continue into the Explorer address bar. Notepad++ or VS Code edits the YAML fine, but keep indentation spaces only. Delete a single project folder under workspaces/ to reindex just that repo.
Frequently asked questions
where is the continue config file
Open ~/.continue/config.yaml (or %USERPROFILE%\.continue\config.yaml on Windows). It lists models, context providers, and docs. Continue also accepts config.json in the same folder. If neither file exists the extension runs on built in defaults.
how do i reset continue code index
Under .continue/workspaces with one folder per indexed project. Deleting a workspace folder forces a clean reindex next launch, which fixes most stale symbol results. The main config survives, so this is safe to try.
how do i migrate continue to a new machine
Copy the whole .continue folder to the same path on the new machine, then sign in again if you use the Hub. Model API keys move with the copy, so treat the folder like any other secrets directory.
Notice an outdated path? Let us know.