Guides

Reading and editing code

The file explorer, the editor and what changed in each run.

The agent writes real files, and you can read and change every one of them.

The file explorer#

The left side of a project lists its files. Use the search box to find files by name or by text inside them. A dependency view lists the dependencies declared in your pom.xml.

Note

The dependency view reads what your build file declares. It is not a resolved dependency graph, so it will not show transitive dependencies.

The editor#

Select a file to open it in the built-in editor. It highlights Java, YAML, XML, JSON and more.

Save with the save button or the usual shortcut. Saves are checked against the version you opened, so you are told if the file changed underneath you.
While an agent run is active the editor is read-only. This stops your edits and the agent's from colliding. Edit after the run finishes.
Very large files are not editable here. If a file is that big, consider splitting it.

You are free to change the agent's code. The next run reads your edits and builds on them.

Files changed#

After a Build run that changes source, the thread shows a Files changed summary. Each file lists its additions and deletions, and you can expand a file to see the diff. Read it before you download, particularly for anything that touches player data or permissions.

Renaming and deleting#

Rename a project from its card or from the project header.
Delete a project from the same places. Deleting is refused while a run is active.

Heads up

Deleting a project does not delete a GitHub repository linked to it. Remove the repository on GitHub yourself if you no longer want it.

The brief#

Every project keeps its original brief. Open the brief page from the project to read it or change it. Changing it does not start a run.

What the agent can see#

On each run the agent works with the text files in your project. Very large files and very large projects may be skipped. See Project structure.