Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions packages/playground/src/server.ts
Original file line number Diff line number Diff line change
Expand Up @@ -2790,8 +2790,9 @@ class PlaygroundServer {
}

try {
const inlineScreenshots = screenshotIncluded !== false;
const dumpString = agent.dumpDataString({
inlineScreenshots: true,
inlineScreenshots,
Comment on lines +2793 to +2795

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep playground response screenshots inline

When the Playground UI turns off “Include screenshot in request” it sends screenshotIncluded: false, but execution still captures screenshots into task.uiContext/recorder for reports. This /execute response is consumed directly by the browser; with inlineScreenshots set to false it contains only midscene_screenshot_ref objects and no screenshot files or image script tags are returned. The visualizer builds replay frames from result.dump and reads screenshot.base64, so replay/report previews for these runs become blank. Keep response serialization inline, or return separately accessible screenshot assets, independently of the model request option.

Useful? React with 👍 / 👎.

});
if (dumpString) {
const groupedDump = ReportActionDump.fromSerializedString(dumpString);
Expand All @@ -2800,7 +2801,7 @@ class PlaygroundServer {
response.dump = null;
}
response.reportHTML =
agent.reportHTMLString({ inlineScreenshots: true }) || null;
agent.reportHTMLString({ inlineScreenshots }) || null;

agent.writeOutActionDumps();
agent.resetDump();
Expand Down