VyroAI

Loading...

Watching the AI Work, and Seeing What Changed

The panel that shows files being written live — and the green-and-red view of exactly what moved.

You do not have to guess what it did

When the AI starts writing, you can watch its work in a panel of its own rather than a spinner. The panel does not open by itself: on a Discord bot, a mod and most other project types, press Live in the editor's tab bar; on a web app, press Code while it writes. Files appear in it as they are written, one after another, with the one in progress marked.

It answers the question people actually have during a long generation — is it doing anything, and is it touching the file I care about? — in one click.

A Minecraft plugin has no live panel. Its tab bar holds only Code and Changes, and the writing streams in the chat column beside the editor instead.

What changed, in green and red

When it finishes, open the Changes tab in the editor's tab bar — it sits beside your open files and carries a count of how many files the run touched. Inside it is the difference, line by line: green for what was added, red for what was taken away, per file.

This is the habit worth forming. Reading the difference takes seconds and is the only reliable way to notice the thing you did not ask for — a config value quietly changed, a method removed along with the bug in it. "It compiled" is not the same as "it did what I wanted".

Reading further back than the chat shows you

A project you have worked on for a while has a longer conversation than the panel puts on screen. When you open a Code Studio project, the chat loads the most recent 20 messages from the server — enough to see where you left off, without waiting for a year of history.

At the top of the chat sits ↑ Load older messages. Each press fetches the next 20, older than the oldest one you already have, and adds them above. Press it as many times as you like: it keeps paging back until the very first message of the project, and the button disappears once there is nothing older left. While a page is on its way the button reads Loading older messages… and cannot be pressed twice.

There is a second button with almost the same name a little lower down, and it does something different. Once the conversation on screen passes 50 entries, only the newest 50 are drawn and the rest are hidden — those are already loaded, just not rendered. That button says Load older messages with the number in brackets, and pressing it draws all of them at once. No fetching, no waiting.

The diff is a view, not a decision: the files are already written by the time you read it. If something in the red half should not have gone, Version History has a save point from before the change — see that article.

On a long generation you can carry on reading the diff of the files that are already done while the AI writes the rest. Nothing has to finish before you start checking it.

Where to next

18 of 37 in Code Studio (IDE) · Last checked 12 September 2026 · Previous: Project Memory