Deep Search: updates for 6.5 #1191
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| @@ -2,36 +2,61 @@ | |||
|
|
|||
| <p className="subtitle">Learn more about Sourcegraph's agentic Code Search tool Deep Search.</p> | |||
|
|
|||
| <Callout type="note"> New in version 6.4. Deep Search is currently in research preview for Enterprise customers with access to Cody and Code Search. Because Deep Search is in research preview, it might change significantly in the future as we make improvements and adjust to user feedback. Please reach out to your Sourcegraph account team to request access. </Callout> | |||
| <Callout type="note"> New in version 6.4. Deep Search is currently in research preview for Enterprise customers. Because Deep Search is in research preview, it might change significantly in the future as we make improvements and adjust to user feedback. Please reach out to your Sourcegraph account team to request access. </Callout> | |||
There was a problem hiding this comment.
Should this say 6.5? Yes we released to some customers in 6.4 but this broader release is for 6.5
|
|
||
| ## Best practices | ||
|
|
||
| - Give the agent a starting point for the search: Mention relevant repositories, files, directories, or symbol names. The more specific you are, the faster the search will be. | ||
| - Give the agent a starting point for the search: use @-mentions to mention relevant repositories, files, directories, or symbol names. The more specific you are, the faster the search will be. | ||
| - Provide reasonably scoped questions. The agent will perform much better if it does not have to read the entire codebase at once. | ||
| - Check the list of sources. This is extremely useful for debugging and understanding where the answer came from. If something is missing, ask a follow-up question and mention the missing source. | ||
|
|
There was a problem hiding this comment.
Since lots of people have gotten stumped on exhaustive use cases, let's provide a bullet point here about how Code Search still kicks ass with exhaustive use cases. CC: @mmanela
Copy: "For use cases where you're looking for exhaustive answers (eg. Find me all files which end with .XYZ file extension from within the X repo that contain the word CODE), Code Search still excels, which Deep Search will only utilize a sample of the results. Deep Search will perform a Code Search query as a source, which you can then use to continue with an exhaustive search within the Code Search product."
Uh oh!
There was an error while loading. Please reload this page.