Existing projects

Reading the change report

Diffs, added and deleted files, the simulation verdict, and how to get your project back.

A project run does not hand you a module; it hands you a change report. That is the list of what was added, modified and deleted, with a unified diff for each file, plus whatever the simulation had to say.

Where it appears

In the right-hand panel, in the same slot a scratch chat uses for generated files. Each file is a row you can expand to see its diff.

rtl/fifo.sv · +4 −1

@@ -18,7 +18,9 @@ module fifo #(
     always_ff @(posedge clk) begin
-        if (!rst_n) wr_ptr <= '0;
+        if (!rst_n) begin
+            wr_ptr <= '0;
+            full   <= 1'b0;
+        end
         else if (push && !full) wr_ptr <= wr_ptr + 1'b1;

One expanded file in the change report. Additions are green, removals are red, and hunk headers are highlighted.

Reading it

Marker	Meaning
added	A file that did not exist before this run.
modified	An existing file that was edited. The diff shows exactly what changed.
deleted	A file the run removed. Check these first; they are the least reversible.
Binary file	Changed, but there is no useful text diff to show.

Very large change sets are capped so the panel stays usable: at most 50 files carry a diff, and a single file's diff is truncated after 400 lines. The files themselves are complete; only the preview is trimmed. Download the workspace if you need to see everything.

The simulation verdict

If the run was able to compile and simulate, you get a verdict alongside the diff. It has three values, and the third one is the important one:

Verdict	Meaning
passed	The testbench ran and reported success in a form we recognise.
failed	The testbench ran and reported a failure.
unknown	It ran, but the output did not match any pass or fail convention we know. Read the log yourself.

Note

Your project follows its own testbench conventions, so unrecognised output is reported as unknown rather than optimistically called a pass. That is deliberately conservative; a wrong green tick is worse than an honest shrug.

Getting your project back

The panel has a download button that gives you a zip of the workspace in its current state, with every edit applied. Unzip it over a copy of your checkout, or diff it against the original; our own bookkeeping files are filtered out of the archive, so nothing of ours ends up in your repository.

Download after the turn you are happy with, not at the end of a long session, if you want a specific intermediate state.
The workspace is not a Git repository; there is no history to roll back to inside it.
Keep your own copy. The workspace is working space, not storage.

When a run fails part way

The agent edits in place, so a run that dies mid-change has already written some of it. The change report is still produced for a failed run, and those partial edits are visible in it rather than being silently discarded. Read the diff before asking for another attempt; you may only need to finish the job rather than restart it.