JARU 0.9.8
- Date: November 2026
- Components: IDE (0.9.8.0) · Windows VM · ESP32 / ESP32-S3 VM · ESP32-P4 VM · ESP32-S31 VM · Compiler
- Previous version: 0.9.7
This version brings one big new feature and a round of fixes:
- AI assistants inside the IDE. Claude and Codex can read the project, change the code, build, run, debug and edit the rooms, the tilemaps, the images and the music, with the IDE in front of you and under your control.
- A code editor that no longer marks errors that aren't errors, and that reloads by itself the files another program changes on disk.
- Fixes in the debugger and in the physics, found while testing the above.
Highlights
- Connect Claude or Codex with a button. In Settings, a checkbox turns the connection on and the Connect Claude and Connect Codex buttons set the assistant up, with no configuration files to edit.
- You see who is working. A badge in the ribbon says AI: Claude or AI: Codex while the assistant does something, and everything it asks for is written in Output with its name in front.
- An assistant can't flash a board on its own: JARU IDE asks you every time.
- The assistant makes whole games: it draws images and sprites, creates tilemaps and rooms, adds rules, writes music, builds, runs the game and plays it by pressing keys to check it.
- The editor stops marking false errors. In the examples it marked 1,360 errors; 49 are left, and those 49 are real.
- The editor reloads what changes on disk, instead of overwriting it when saving.
- A reliable Watch window: it no longer shows values from the previous stop.
⚠️ Breaking changes
| Change | What to do |
|---|---|
| Programs compiled with 0.9.8 need firmware 0.9.8. A 0.9.7 firmware refuses them when loading, with the message "Program version 0.9.8 uses bytecode newer than this VM (0.9.7). Update the firmware from the IDE". | Flash the VM firmware (Flash Firmware) on each board before uploading programs compiled with 0.9.8. |
There are no changes in the language or in the API: 0.9.7 programs compile and work the same.
AI assistants (new)
JARU IDE talks to assistants through MCP (Model Context Protocol). The assistant is a separate program, with your account: Claude Desktop, Codex or Claude Code. You ask in your own words in its window, and you see what it does in the IDE. Step by step, in Connecting an AI assistant.
It is not the same as AI Agents, which stays where it was: there it is the IDE that calls a model, with your key, to generate I2C drivers.
Connecting
- The connection comes turned off. You turn it on in Config › IDE › Settings, with the Let AI assistants connect to this IDE (MCP) checkbox and Apply config: right away, without restarting.
- Connect Claude hands the JARU IDE extension to Claude Desktop, and Claude shows it with its install button. It also works in the Code tab of Claude Desktop. After updating JARU IDE you have to press it again: Claude keeps its own copy of the extension.
- Connect Codex adds JARU IDE to the configuration of Codex. It asks first, saves a copy of the file and touches nothing else in it. After updating JARU IDE you don't have to repeat it.
- Claude Code, the one in the terminal, is connected with a command:
claude mcp add --transport stdio --scope user jaru-ide -- "C:\Program Files\JARU IDE\Mcp\jaru-mcp.exe". - The installer leaves both pieces in the
Mcpfolder of the IDE: the connection program,jaru-mcp.exe, and the Claude Desktop extension,jaru-ide.mcpb.
What it can do
There are 62 tools. With them the assistant can (Working with an AI assistant covers it):
- Project: see its files, create a project and open another one; create, rename and delete files (deleted ones go to the Recycle Bin).
- Code: read the open file and the errors the editor marks, and change the text in the editor itself, where you see it and can undo it.
- Reference: the IDE gives it the reference of the language, of the modules, of the behaviours and of the rules, so there is no need to teach it JARU.
- Building and running: build, run on Windows, read what the program 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.
- Debugger: set breakpoints, step through the code and read variables.
- Rooms: create rooms and change their objects, zones and routes, their layers, rules, variables, templates, state machines and settings. And, for the game, its variables, its controls and its frames per second.
- Tilemaps: create tilemaps and change their cells, their size, their tileset and their mode.
- Images and sprites: draw images, import them from a file and define the frames, the animation, the pivot and the collider of a sprite.
- Music: write a whole piece of music, with its instruments, and import a MIDI file.
- 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.
Who is working
- The ribbon badge. With the connection on it says AI: on. While an assistant works it says AI: Claude, AI: Codex or, for any other, AI: active; it goes back to AI: on 10 seconds after the last thing it did. A click on it opens Settings.
- Output. Everything an assistant asks for is written with
[CLAUDE],[CODEX]or[AI]in front. - Boards. To send the program to a board, JARU IDE asks every time, in a dialog that says which assistant is asking, which project, which board and which port. With no answer in 120 seconds, it closes as No. When the assistant runs the program it always does so on Windows: with a board as the build target it doesn't run it.
- With both assistants connected at the same time, the badge names the last one that did something.
Keep in mind
- The assistant only works with JARU IDE open and the connection on.
- It can't hear: it can write music, but listening to it is up to you.
- The images, sprites and tilemaps it changes are saved right away and can't be undone; the code and the rooms can.
- If the IDE is asking you something in a dialog, the assistant waits and after 20 seconds gets a notice that the IDE is busy.
VMs
- Physics, one-way platforms (FIS-5). In a room with several physics steps per frame (
scene.stepRate), a body could fall through a one-way platform when landing. With one step per frame it didn't happen. It is in the Windows VM and in the firmware of every board. - Debugger (Windows): the Watch window no longer loses readings. With the program stopped, when several variables were asked for in a row some rows kept the value from the previous stop and, now and then, the session stopped pausing.
- Debugger (Windows): a breakpoint set before starting also fires in a large program. Before, it never fired; set with the session already running, it did.
IDE
Code editor
- It reloads what changes on disk. If another program changes a file you have open and untouched, the tab reloads by itself and Output says so. If you had unsaved changes it is left alone, and the IDE warns you that saving will overwrite what is on disk. Before, the IDE didn't notice.
- False errors. The editor marked as errors code that compiled. Four causes, all four closed:
- A file of the program now sees what all the others declare, as when running. A game split into several files came out full of "is not defined".
- An
importof a file that is on disk but not in the project tree is resolved, as the compiler does. - A string with an escaped quote (
\") is read whole. Before, it was cut there and the rest was read as code; the syntax colouring had the same fault. Display.draw.coloris no longer marked, and a variable is no longer taken for a module.
Running and debugging
- Run on a board: if it had to build before sending, when it finished the ribbon stayed as if it were still building, with Run, Stop and Debug greyed out. Not any more.
Other improvements
- Settings has a new row for the connection with assistants: the checkbox and the Connect Claude and Connect Codex buttons.
- Checkboxes and radio buttons show well on the dark theme: before, they could hardly be told apart from disabled ones.
Documentation
- Three new pages in the IDE section: Connecting an AI assistant, Working with an AI assistant and A game made with an assistant, with a real example step by step.
Known issues
- Connect Claude has been tested with Claude Desktop for Windows. If JARU IDE can't find it, the button gives the path of the extension so you can install it by hand from Claude Desktop's settings.
- Claude Desktop warns when installing the extension that it will have access to the computer and that it has not verified who made it.
Input.justPressedcan miss presses. Workaround: readInput.pressed()once per frame and compute the edges yourself.- Renaming, moving or deleting an asset does not rebuild the resources of the scene editor's Play. Workaround: delete
Build/assets.stampbefore pressing Play, or build with Build › Compile, which always rebuilds them. - Compiler: indexing what a call returns,
f(x)[0], does not work. Workaround: store it in a variable first. readLine()on a board gets no input over serial: the examples that ask for input (CheckPrime, Factorial_ForLoop, FibonacciGenerator and Palindromes) keep waiting. They work on Windows.
The full list, with all the known issues of 0.9.8 and how to work around them, is in Known issues.
Installation / update notes
- Windows IDE: installer
JARU_IDE_0.9.8_Setup. What to do if you upgrade from 0.9.7. - Flash the VM firmware (Flash Firmware) on each board before uploading programs compiled with 0.9.8: a 0.9.7 firmware refuses them, with a message that says so.
- Assistants: the connection comes turned off. If you want to use it, turn it on in Settings and connect your assistant with its button.