Edit mode modifies multiple files based on your requirements and project context, with support for iterative changes and code reviews.
Edit mode is available in Visual Studio Code only. Qoder CN IDE and the JetBrains IDE plug-in are not supported.
Edit mode was previously named AI Developer. Update to V2.5.0 or later in VS Code and JetBrains IDEs.
Core capabilities:
-
Project-level changes: Modify multiple code files based on your task description. Use multi-turn conversations to optimize code or roll back snapshots.
-
Precise editing: Code modifications stay strictly within the provided context and specifications.
-
Fast execution: Follows your task description and context for rapid edits without complex task planning. Faster than Agent mode.
-
Tool use: Uses file reading, in-project semantic search, and file editing to accomplish code modifications.
Multi-file edits
Follow these best practices for multi-file edits:
-
Provide clear requirements: Specify which code to modify, then list your requirements with a clear objective and step-by-step expectations.
-
Specify context: Select relevant code files, images, codebases, and code changes to define the modification scope. Comprehensive context helps generate better solutions and code suggestions.
-
Define generation criteria: Specify requirements should follow when generating code, such as programming language, coding standards, or format (for example, "Add comments to each method"). Save project-wide requirements in the rules file. For more details, refer to Rule settings.
-
Use snapshots: If AI-generated content doesn't meet expectations, use snapshots to revert to previous conversation steps and code states, then iterate on your requests.
File-level unit test generation (UnitTest)
Unit test generation creates test files in batch for code changes or selected code files. Provide the code and your requirements — automatically creates test plans, generates and runs test cases, and fixes errors.
Unit test generation is supported in IntelliJ IDEA only.
Select code and enter requirements
-
Open the AI Chat panel and switch to Edit mode.
-
Click ➕ in the input box or type
#to select the relevant context. -
Enter your instructions. Include unit test requirements in the description.
-
Submit your requirements. detects the intent and starts unit test generation.
Confirm the environment
automatically detects your local environment: Java version, build tools, test frameworks, and mock frameworks. If multiple versions are detected, select the one you need. If cannot identify the version, click How to Fix for configuration instructions.
Select methods to test
After the environment check passes, analyzes the files and generates a test plan. Select the methods to test and click Confirm. generates unit test cases for each selected method.
-
Select 1 to 20 methods per generation.
-
The estimated build time is displayed after you select methods.
View generation progress
generates unit test cases for the selected methods, then compiles, runs, and fixes the results. The following table describes the status indicators.
|
Status |
Description |
|
|
Passed |
|
|
Compiled but failed at runtime |
|
|
Compilation failed |
After generation completes, merges passing test cases into a final test file named after the source file. You can choose to keep or discard code that failed compilation. Click Confirm to compare the test file with the original.
Review and accept test code
The test file appears in the Working Space. Click Diff or select a file to view changes in the Diff View. Review, modify, accept, or reject each change, then click Accept to apply the code to your project.
