Deep Search now honors an admin-defined exclusion list. Anything matched by a context filter is invisible to the agent. The excluded content never shows up in Deep Search's answers, and it can't be read, diffed, or resolved by any Deep Search tool.
A site admin can configure filters under Admin → Configuration → Advanced configuration, inside the experimentalFeatures block. Each rule can match repositories by name, file paths, or both
"experimentalFeatures": {
"deepSearch.contextFilters": {
"exclude": [
// Hide an entire repository.
{ "repoNamePatterns": ["^github\\.com/acme/secrets$"] },
// Hide secret-bearing files in every repository.
{ "filePathPatterns": ["\\.env$", "\\.pem$"] },
// Hide deployment config in certain repositories only.
{
"repoNamePatterns": ["^github\\.com/acme/backend$"],
"filePathPatterns": ["^deploy/", "^config/prod/"]
}
]
}
}
Config changes apply to the next Deep Search run, no restart is required.
Read more in our context filters docs, which cover the matching pattern syntax, how repoNamePatterns and filePathPatterns combine, and working examples of each rule shape.
