Skip to main content
Open a supported file or application link from chat, Task Detail, or Files. The workspace panel can show multiple tabs alongside the conversation. Use its tab controls to close a tab, close other tabs or tabs to the right, resize, expand, or restore the panel. Closing the panel does not delete the underlying output.

Review a file

Confirm the file name and project/task context, inspect the preview, and use Source or Download when you need the original content. Open Task Detail alongside the result when acceptance criteria matter. A file preview shows content. It does not establish that the result meets every requirement or has been tested.

Review an image

Use Image review to draw markup on the image and add a comment. Change the markup color, undo, or clear your drawing as needed. Choose Use in chat to send the selected review context into the composer, then review the message before sending. Describe the requested change precisely, for example: “Increase the spacing between the heading and illustration in the marked area.”

Review a live application

A live preview runs the project’s supported preview workflow. Wait for preparation to finish; if startup fails, read the reported issue and ask the agent to repair the intended project. The Browser area supports a URL, navigation, and opening externally. Some websites prevent embedding, so external opening may be required. Use Review preview to select an element or draw on the preview and add feedback. Element inspection can be unavailable for an external page; drawing and comments can still be available.

Share the right result

Share preview, when enabled, creates an expiring link to the isolated preview. Anyone with that link can view it until it expires, so review the visible content before sharing. A preview link is different from the durable public URL created by Publish app. Neither a ready preview nor opening a Browser tab proves that browser tests passed.

Browser Test

Browser Test is a separate verification workflow for an exact preview. Request it explicitly when you need interaction, responsive, or browser evidence. Inspect the passed report and the tested version before using it as proof. A failed or unavailable test should remain visible as a verification gap. If the project changes after testing, request checks for the changed result.