Preserve pending design edits through Inspect mode and version previews

User intention

Inspect a rectangle I just added to my design.

Preview an older version of my design.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Follow the newly drawn rectangle into Inspect, then return to Dashboard and reopen the same file. The rectangle is missing after reopening.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

The newly drawn rectangle remains available after entering Inspect, returning to Dashboard, and reopening the same file.

How is it judged?

01 · Given

Restore the data and starting state.

An editable design file is open on an empty page. Edits are saved automatically in the background.

02 · When

Perform the interaction.

The user draws a rectangle, switches the sidebar to Inspect before autosave finishes, and stays there longer than the autosave interval. They then return to Dashboard and reopen the same file.

03 · Judge

Rationale: Inspect is a read-only mode for viewing a design object's properties and code. Switching to it after editing should preserve work still being saved in the background, so the user can inspect the design and return to the same edits later.

Require

Previously pending edits remain persisted or recoverable through Inspect mode and are available when the same file is reopened.

Allowed

The queue may flush before switching, continue saving in Inspect, or resume submission after leaving Inspect.
A persistent local queue may restore the edit after reload.
Inspect's read-only presentation may vary.