Context

Qoder CN supports rich context in AI chat, such as code files, directories, images, and Git commits. Combine context with prompts to describe your requests.

​

Add context

Add context in three ways:

1. Click the add context button in the input box.
2. Type # or @ in the input box to open the context selection window, then type to search for files.

3. Drag and drop or copy and paste code files and images to add them as context. Available only in JetBrains IDEs.

For context types like #file (@file), #folder (@folder), #gitCommit (@gitCommit), #teamDocs, and #rule (@rule), you can search for and select multiple items. In JetBrains IDEs, you can also drag context tags into your prompt to assemble requests.

​

Supported context types

Qoder CN offers various context types. Combine them with each other or with natural language to build a complete prompt. Supported context types: file, folder, image, codebase, teamDocs, codeChanges, gitCommit, and rule.

​

#file

To ask questions about or modify one or more files, type #file in the input box. You can select multiple files. In JetBrains IDEs, you can also drag and drop or copy and paste code files. Tips:

• After you select a file, Qoder CN recommends related files. Click a file name to add it.
• To add a specific file to your prompt, you can type # to select it.

​

#folder

To ask questions about or modify a specific code module, add the relevant project directory as context. Useful for batch operations like searching, code refactoring, adding comments, or generating unit tests.

​

#image

To use an image to generate code, fix bugs, or create visual representations, click #image in the context selection window. You can also copy and paste a file or screenshot directly. For example, generate a frontend page from a design file.

​

#codebase

To perform a semantic search across the entire project, add #codebase as context. Qoder CN searches the project codebase for the most relevant code snippets. For example, ask "How is user authentication implemented?" without specifying any files.

​

#codeChanges

To ask questions about or modify code changes in the current Git staging area, add #codeChanges as context. For example, before pushing, ask Qoder CN to perform a code review, suggest optimizations, or add unit tests for staged changes.

​

#gitCommit

To ask questions about code changes from a specific Git commit, use #gitCommit to add the commit information. For example, select one or more commits to troubleshoot issues, fix bugs, or generate unit tests.

​

#teamDocs

To use your enterprise knowledge base for Q&A or code generation, add #teamDocs. Qoder CN searches the knowledge base and uses retrieved information as context. For example, use your team's component guidelines to generate code.

​

#rule

The #rule context applies a system prompt with preset instructions. This persistent, reusable context is included in every request, ensuring consistent model behavior for code generation, refactoring, and workflow automation.