continuedev / continuedev/continue
Exclude folders / files?!
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Description
I have this config.yaml entries:
context:
- provider: code # @code – Symbole / Funktionen im Codebase suchen
- provider: file # @file – Einzelne Datei anhängen
- provider: folder # @folder – Ganzen Ordner anhängen
- provider: currentFile # @currentFile – Aktuelle Datei automatisch einbeziehen
- provider: terminal # @terminal – Letzten Terminal-Output einbeziehen
- provider: problems # @problems – VS Code Problembereich einbeziehen
- provider: diff # @diff – Aktuellen Git-Diff einbeziehen
- provider: open # @open – Alle aktuell geöffneten Tabs einbeziehen
- provider: codebase # @codebase – Gesamten indizierten Workspace durchsuchen
- provider: safe-folder
params:
#includes: ["*.py"]
excludes: ["build/", "dist/", "__pycache__/", "TMP/", "TEMP/", "Documentation/"]
safe-folder is not known (sure)!
How can you give an "ignore list" of files / folders to continue? Like when you use file or folder or currentFile and so on that if they are on the "ignore list" that they are NOT used for the ai.
It's not only to safe some tokens, maybe even to not deliver sensitive data to a cloud ai...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how config.yaml is loaded and how the reported context providers—file, folder, currentFile, and related sources—select content. Determine where a shared include/exclude rule could apply without relying on the unknown safe-folder provider. Done means configured files and folders are excluded from AI context, including potentially sensitive data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100