Code editor
Use the editor for manual text/code changes and the AI editing panel. Open the target text file from Files and check its project path.
Open
Read and locate code
Use line numbers, search and navigation. Highlighting helps reading but does not validate code. Enable wrapping for long lines when useful. Relative project paths refer to the workspace; a filename alone does not identify which copy is open.
Save and back up
Review manual edits, save, then reopen or read back the changed section. Look for .bak files generated by the editor. They can help recover recent content; keep longer history in version control.
Use the AI panel
- Specify the file, scope and behavior: “Only change this function and preserve its callers.”
- Inspect the read/edit results and file changes.
- Save and run the project's checks; verify disk and editor content agree.
Concurrent manual and AI changes can conflict. Preserve your work and have the Agent reread the latest content. See developer hooks for the edit interception and commit callbacks.
Verify the result
Read back text changes, or run relevant tests, builds or previews for code. Saving only confirms a write. See change review for Agent diffs and records.