Deprecated codebase context provider - use the new codebase awareness approach instead
@Codebase
context provider has been deprecated in favor of a more integrated approach to codebase awareness. Please refer to our Guide on Making Agents Aware of Codebases and Documentation for the recommended approach.@Codebase
or @Folder
context providers, please migrate to the new approach outlined in our codebase and documentation awareness guide. The new approach provides:
@Codebase
context provider, preserved for reference
Continue indexes your codebase so that it can later automatically pull in the most relevant context from throughout your workspace. This is done via a combination of embeddings-based retrieval and keyword search. By default, all embeddings are calculated locally using transformers.js
and stored locally in ~/.continue/index
.
transformers.js
cannot be used in JetBrains IDEs. However, you can
select a different embeddings model from the list
here.@Codebase
or @Folder
in the input box, and then asking a question. The contents of the input box will be compared with the embeddings from the rest of the codebase (or folder) to determine relevant files.
foo
method in the bar
class, following the patterns seen in other subclasses of baz
.@Folder
to ask questions about a specific folder, increasing the likelihood of relevant results
@Folder
instead of @Codebase
foo
function is called”bar
function and update usages”@codebase
context provider, which are the same for the @folder
context provider:
nRetrieve
nFinal
useReranking
nRetrieve
results, then will use an LLM to select the top nFinal
results (default: true)
.gitignore
files in order to determine which files should not be indexed. If you’d like to exclude additional files, you can add them to a .continueignore
file, which follows the exact same rules as .gitignore
.
Continue also supports a global .continueignore
file that will be respected for all workspaces, which can be created at ~/.continue/.continueignore
.
If you want to see exactly what files Continue has indexed, the metadata is stored in ~/.continue/index/index.sqlite
. You can use a tool like DB Browser for SQLite to view the tag_catalog
table within this file.
If you need to force a refresh of the index, reload the VS Code window with cmd/ctrl + shift + p + “Reload Window”.