⏩ Continue is the leading open-source AI code assistant. You can connect any models and any context to build custom autocomplete and chat experiences inside VS Code and JetBrains
[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement
Problem
Codebase is very useful for automatically finding context, but I want to be able to add arbitrary additional data to it. For example, I may have a separate repo for documentation and would like to include that for automatic local retrieval of relevant context, or have local notes on tasks/designs etc. Think analyzing your notes/todos/future plans for context as part of your codebase.
An additional folder makes sense as either indexed as part of the Codebase provider or into the Docs provider. It's easy to imagine local docs for either use case.
Solution
I'm not sure what makes the most sense for implementing. Either including some way to specify additional folders to Codebase index (e.g. .continueinclude file), or a way for the Docs provider to specify a local folder or a git repo, or both.
I workaround this today by taking advantage of how Continue doesn't respect the global .gitignore settings. So I globally ignore a .docs directory, and add any additional documentation in there.
Validations
Problem
Codebase
is very useful for automatically finding context, but I want to be able to add arbitrary additional data to it. For example, I may have a separate repo for documentation and would like to include that for automatic local retrieval of relevant context, or have local notes on tasks/designs etc. Think analyzing your notes/todos/future plans for context as part of your codebase.An additional folder makes sense as either indexed as part of the Codebase provider or into the Docs provider. It's easy to imagine local docs for either use case.
Solution
I'm not sure what makes the most sense for implementing. Either including some way to specify additional folders to Codebase index (e.g.
.continueinclude
file), or a way for the Docs provider to specify a local folder or a git repo, or both.I workaround this today by taking advantage of how Continue doesn't respect the global
.gitignore
settings. So I globally ignore a.docs
directory, and add any additional documentation in there.