Editing files and version history
Edit any file in the built-in code editor, how saving works, and how to restore an earlier version of a project.
Updated
On this page
Every project opens in a full code editor with a file tree.
#Editing
- Click any file in the tree to open it in a tab.
- Edits save automatically two seconds after you stop typing. Ctrl+S (Cmd+S on macOS) saves immediately.
- Your edits become part of the project: the next chat request works from what is actually in the files, including your changes.
#Without a plan: the start of each source file
On the Free plan the editor shows the first lines of each source file (Java, Kotlin, Skript, Python, JavaScript, HTML, CSS and the like). The rest of the file is marked as hidden, with the number of lines, and a box offers three ways on: See plans to see the full code, Try it now to test the project on a real server, and Download to get the files.
- Configuration files (plugin.yml, config.yml, pom.xml, build.gradle, package.json and other settings) are shown and editable in full.
- Source files are changed through the chat: ask Codexe for the change and it edits the complete file. Saving a source file by hand needs a plan.
- Your project is always complete: it builds, runs on test servers and downloads with every file whole.
- With Pro, Business or Enterprise every file is shown in full.
#Copying code
Copying code from the editor, the chat and the other pages that show code is turned off on every plan. The files leave Codexe through a download.
#Version history
Open History in the project toolbar to see earlier versions of the project, one for each AI change. Selecting a version restores the files as they were at that point. This is useful when a change went in the wrong direction.
#Web and 3D previews
- Static websites open on a test server in the project page, with a button to open it in a new tab.
- Blockbench models have a 3D preview.