Chat with the AI assistant in your code editor or via the Sourcegraph web app to get intelligent suggestions, code autocompletions, and contextually aware answers.
-
-
You can **chat** with Cody to ask questions about your code, generate code, and edit code. By default, Cody has the context of your open file and entire repository, and you can use `@` to add context for specific files, symbols, remote repositories, or other non-code artifacts.
You can do it from the **chat** panel of the supported editor extensions ([VS Code](/cody/clients/install-vscode), [JetBrains](/cody/clients/install-jetbrains), [Visual Studio](/cody/clients/install-visual-studio)) or in the [web](/cody/clients/cody-with-sourcegraph) app.
@@ -103,71 +101,3 @@ If Cody's answer isn't helpful, you can try asking again with a different contex
- **Public knowledge only**: Cody will not use your own code files as context; it’ll only use knowledge trained into the base model.
- **Current file only**: Re-run the prompt again using the current file as context.
- **Add context**: Provides @-mention context options to improve the response by explicitly including files, symbols, remote repositories, or even web pages (by URL).
-
-
-
-The enhanced chat experience input can be accessed from the chat panel of the supported editor extensions (VS Code and JetBrains) and the web app. It combines light code search, AI-powered chat, and agentic capabilities into a unified developer interface. It's designed to accelerate the entire developer workflow by providing a more intuitive and powerful way to interact with code.
-
-## Prerequisites
-
-To use Cody's chat, you'll need the following:
-
-- [Sourcegraph Enterprise Starter](https://sourcegraph.com/pricing) or [Enterprise account](https://sourcegraph.com/pricing)
-- A supported editor extension [VS Code](https://marketplace.visualstudio.com/items?itemName=sourcegraph.cody-ai), [JetBrains](https://plugins.jetbrains.com/plugin/9682-cody-ai-coding-assistant-with-autocomplete--chat) installed or use via Web app
-
-## Key features
-
-The enhanced chat experience includes everything in the Free plan, plus the following:
-
-## Smart search integration
-
-The smart search integration enhances Sourcegraph's chat experience by providing lightweight code search capabilities directly within the chat interface. This feature simplifies developer workflows by offering quick access to code search without leaving the chat environment.
-
-The integration delivers personalized search results ranked by your contribution history, with frequently accessed repositories appearing higher in results. Users can view code snippets with relevant context and open files directly in their editor.
-
-Search results automatically become available as context for follow-up queries, with flexible controls for selecting which results to include. While optimized for keyword-style queries and searching across a few repositories, this integration complements rather than replaces the full [Code Search](/code-search) product, which remains the recommended tool for comprehensive enterprise-wide code search.
-
-## Context-aware responses
-
-Search results generated through smart search integration can be automatically used as context for follow-up queries. Here's what happens with each scenario:
-
-### Search responses
-
-* Search results can be used directly as context for follow-up queries
-* Users can select which search results to include as context using checkboxes
-* By default, all search results are added as context
-* A context chip shows the number of search results being used (e.g., "10 code search results")
-* Users can remove the context chip if they don't want to use it for follow-ups
-
-### Chat responses
-
-Executing terminal commands for additional context is an experimental feature.
-
-* Performs background searches for context
-* Retrieves full context from files, symbols, remote repos, and web pages
-* Can execute terminal commands (with permission) for additional context
-* Creates personal notes usable across chat sessions
-* Pulls in [OpenCtx](/cody/capabilities/openctx) providers for additional context
-
-## How does chat work?
-
-The following is a general walkthrough of the chat experience:
-
-1. The user enters a query in the chat interface
-2. By default a user gets a chat response for the query
-3. To get integrated search results, toggle to **Run as search** from the drop-down selector or alternatively use `Cmd+Opt+Enter` (macOS)
-4. For search:
- - Displays ranked results with code snippets
- - Shows personalized repository ordering
- - Provides checkboxes to select context for follow-ups
-5. For chat:
- - Delivers AI-powered responses
- - Can incorporate previous search results as context
-6. Users can:
- - Switch between search and chat modes
- - Click on results to open files in their editor
- - Ask follow-up questions using selected context
- - Use `@` to add context for specific files, symbols, remote repositories, or other non-code artifacts
-
-
-
diff --git a/docs/cody/capabilities/query-types.mdx b/docs/cody/capabilities/query-types.mdx
deleted file mode 100644
index c6d1de2e0..000000000
--- a/docs/cody/capabilities/query-types.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
-# Chat Query Types
-
-
This page lists all the query types that will return search results with the Sourcegraph chat.
-
-Query types are only supported on Enterprise Starter and Enterprise plans.
-
-## Symbol Search
-
-Symbol Search is a query type or workflow that helps developers understand how specific symbols (like functions, variables, or hooks) are used across a codebase by combining search results with contextual analysis through chat.
-
-It enables developers to explore and understand symbol usage patterns through a two-step process. First, developers search for a specific symbol (like `useCallback`) using Sourcegraph Chat, which returns relevant code snippets from across the codebase.
-
-These search results are automatically preserved as context for follow-up chat interactions. Developers can refine their understanding by selecting specific search results and asking natural language questions about the symbol's usage patterns. The chat will analyze the selected code context and provide a comprehensive summary of how the symbol is implemented and used throughout the codebase.
-
-### Try it
-
-1. Query for `= useCallback`
-2. Select a subset of the search results which include usage for `useCallback`
-3. Follow up and ask Sourcegraph chat `Summarize how useCallback is used`
-
-### Example
-
-
-
-## File Search
-
-Search is a query type or workflow that enables users to locate specific files across repositories and perform targeted analysis on the selected files through natural language follow-up queries.
-
-File Search simplifies finding and analyzing specific file types across your codebase. Unlike traditional code search, this workflow allows you to identify relevant files (for example, all `package.json` files), select the specific files you want to analyze, and then ask follow-up questions about the selected files.
-
-This two-step approach is particularly powerful when analyzing patterns or extracting information from similar files spread across multiple repositories. For instance, you could identify all configuration files, select the ones from relevant services, and then analyze their contents for inconsistencies or gather specific information through natural language queries.
-
-### Try it
-
-1. Type `package.json`
-2. Check the checkbox next to the results you want to analyze
-3. Follow up with `List all the dependencies used across these package.json files`
-
-### Example
-
-
-
-## String Literal Search
-
-String literal search is a query type or workflow that allows you to find exact text matches by enclosing your search term in quotes. This ensures precise matching instead of keyword-based results.
-
-When you enclose the text in quotes like `" authInfo: async provider =>"",` Sourcegraph performs an exact match search rather than keyword matching. After finding relevant files, you can select specific ones to analyze and ask follow-up questions about their contents - creating an interactive workflow combining precise search and contextual code analysis.
-
-### Try it
-
-1. Start a new chat with `"authInfo: async provider =>"`
-2. Select a subset of the search results which include usage for the string
-3. Follow up with `Summarize the contents`
-
-### Example
-
-
-
-## Error Lookups
-
-Error Lookups is a conversational workflow for Sourcegraph chat that helps developers understand error messages by providing plain-English explanations of when and why specific errors occur in their codebase and external service calls.
-
-Developers can use Error Lookups to understand error messages occurring in their codebase. When encountering an error, especially from external services or dependencies, developers can use chat to:
-
-1. Search for specific error messages across their codebase
-2. Select relevant files where the error is thrown or handled
-3. Request a natural language explanation of the error's context, triggers, and implications
-
-The workflow combines Sourcegraph's code search capabilities with AI-powered analysis to provide developers with a clear, contextual understanding of error scenarios. Instead of having to dig through docs or source code manually, developers can quickly grasp the following:
-
-* The specific conditions that trigger the error
-* The underlying reasons for the error occurrence
-* Common scenarios where this error might appear
-* Potential approaches to handling or preventing the error
-
-This approach helps developers make more informed decisions about error handling and debugging, reducing the time spent deciphering cryptic error messages or searching through external docs.
-
-### Try it
-
-* Query for `"unsupported platform"`
-* Select the file(s) where the error is thrown
-* Follow up with "Explain when and why this error is thrown"
-
-### Demo
-
-
diff --git a/src/data/redirects.ts b/src/data/redirects.ts
index da231f77a..bae7dfbd4 100644
--- a/src/data/redirects.ts
+++ b/src/data/redirects.ts
@@ -6811,6 +6811,13 @@ const redirectsData = [
permanent: true
},
+ //Rmv Query types permanentaly:https://sourcegraph.com/docs/cody/capabilities/query-types
+ {
+ source: "/cody/capabilities/query-types",
+ destination: "/cody/capabilities/chat",
+ permanent: true
+ },
+
];