Working with an AI assistant
Once the assistant is connected (Connecting an AI assistant), you talk to it in its window and it works in your JARU IDE: in the project you have open.
You don't need to teach it JARU. The IDE itself gives it the reference of the language and of its modules, and lets it see the errors the editor marks and what the compiler says.
What it can do
| With… | The assistant can… |
|---|---|
| The project | See its files, create a new project and open another one. Create, rename and delete files. |
| The code | Read the open file and the errors the editor marks, and change the text in the editor itself. |
| Building and running | Build, run the program on Windows, read what it prints and stop it. |
| The running game | See a screenshot of its window, press keys, and pause it to play it one key press at a time. |
| The debugger | Set breakpoints, step through the code and read the value of variables. |
| The rooms | Create rooms and change their objects, zones and routes, their layers, their rules, their variables, their templates and their settings. |
| The tilemaps | Create tilemaps and change their cells, their size and their tileset. |
| The images and the sprites | Draw images, import them from a file and define the frames and the animation of a sprite. |
| The music | Write a piece of music and bring one in from a MIDI file. |
| The game | Change its variables, its controls and its frames per second. |
| The boards | See the boards of the project and the ports, read what a board prints, add one from a board profile, choose the build target and send the program when you accept it. |
What to ask for
Ask as you would ask a person who has the IDE in front of them. To get started:
Explain what this project does and how it is organised.
Build the project and fix the errors that come up.
Run the game, press the jump key and tell me what happens.
The player falls through the floor. Use the debugger to find out why.
Add a platform to the room that moves from side to side.
It helps to tell it what you want to achieve, and not only what to change: it builds, runs and checks the result by itself.
A complete case, with graphics, a room and music, is in A game made with an assistant.
Save a version of the project with Git. If you don't like the result, you can go back.
What to keep in mind
Where you see its changes
- The code and the rooms it changes in the editor, in front of you: you see it right away and you can undo it.
- The images, the sprites and the tilemaps are saved right away, and can't be undone.
- A file it deletes goes to the Recycle Bin.
- Renaming a file doesn't change the files that name it: ask it to check them.
When building and running
- When the assistant builds, it saves first whatever you have unsaved. The Compile button of the IDE doesn't: it builds what is on disk.
- The program runs on your screen, in the usual window. The assistant sees it through screenshots.
- It only runs on Windows. With a board as the build target, it doesn't run.
- To send the program to a board, JARU IDE asks you every time (Sending the program to a board).
What it can't do
- It can't hear. It can write music, but not listen to it: that part is yours.
- It doesn't work with the IDE closed, or with the connection off.
- It can't get past a dialog. If the IDE is asking you something, the assistant waits and, after 20 seconds, gets a notice that the IDE is busy. Answer the dialog and ask again.
With two assistants
Claude and Codex can be connected at the same time and work on the same project. The badge shows the name of the last one that did something, and Output writes down each request with the name of who made it (Who is working).