Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/deep-search/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,12 @@ You can reuse the same [search contexts](/code-search/working/search-contexts) y

Search contexts are useful when you want to keep Deep Search focused on a specific part of your codebase, such as a team's repositories, a product area, or another shared scope used across your organization. Limiting Deep Search to a smaller set of repositories can help it search faster and produce more focused, higher-quality answers.

Query-based search contexts can include repository filters as well as file, language, case, and content-style filters. Deep Search can use these contexts for code search, but its repository-listing step can only enumerate contexts that are defined by repository constraints. If Deep Search reports that the active search context cannot be listed, either:

- Ask Deep Search to search directly within the selected context instead of listing repositories first.
- Change the selected search context to use repository-only constraints, such as `repo:`, `rev:`, `fork:`, `archived:`, `visibility:`, or supported repository metadata predicates like `repo:has.topic(...)`.
- Create a repository-defined search context for scopes that Deep Search should list as repositories.

To learn how to create and manage search contexts, see [Search contexts](/code-search/working/search-contexts).

## Using @-mentions
Expand Down