Export Studio¶

Export Studio turns an exercise dashboard into a focused comparison that can be shared as a live view or downloaded as a standalone artifact.

Open a strategy comparison dashboard and select Export view, or replace strategy-compare with strategy-export in an exercise report URL:

/ui/reports/strategy-export.html
/ui/reports/strategy-export-<connector>-<exercise>.html

Compose A Comparison¶

The studio supports:

• selecting only the runs that belong in the comparison
• labeling runs by run name, model, coding harness, model and harness, or an arbitrary display name
• assigning any color and solid/dashed/dotted line style to each run
• highlighting a run, keeping it normal, or graying it into context
• score trajectory, best-candidate run scatter, aggregate group scatter, and cumulative-token charts
• active time, elapsed time, working tokens, API-equivalent cost, and candidate-number axes
• logarithmic or linear score scales
• optional candidate markers, endpoint labels, legend, and source footer
• optional finishing scores appended to run names in endpoint labels and legends
• custom eyebrow, title, and explanation text
• draggable text boxes with configurable text, width, size, color, and optional background
• draggable arrows with movable endpoints, color, and line-width controls
• 16:9, square, and 4:5 output formats

Compare groups applies any group assignments without changing which runs are selected. Presets can assign runs by model, coding harness, effort level, experimental skill usage, or the exact experimental skill set. Groups can also be created, renamed, colored, and assigned per run. Turning comparison off returns to each run's own visual settings without deleting those assignments.

Label preset controls the compact names printed beside the chart and in the legend. Choose Model + harness to replace long experiment names with labels such as claude-opus-5 / Claude Code. Model-only and harness-only presets are also available. You can edit any generated display name afterward; the studio then marks the label mode as Custom labels. A dashboard export keeps the run names unless Only best run by is active. When it is active, the studio uses the exact selected dimensions for compact labels: Model, Harness, Skill, or any combination of them. The selector identifies this as Dashboard grouping.

Finishing score in names is independent of label presets and dashboard grouping. It appends each run's best valid score in the selected time window, including the objective unit, for example gpt-5.6-sol / Codex (981 cycles). It works with run names, generated presets, and manually edited labels.

The experimental-skill presets deliberately ignore required plumbing and coordination skills: scorebench, progress-logging, superpowers, skill management helpers, OpenAI documentation, and Arbor coordinator skills. A run is labeled Skill only when it used an optimization or knowledge skill such as problem-agnostic-optimization. This keeps the treatment definition aligned with controlled skill-versus-no-skill experiments.

Clicking a chart line or legend item focuses that run and grays the other selected runs. Clicking the focused run again restores the configured view.

Best candidate shows one point per run. Use the Tokens x-axis to compare the working-token budget at each run's best score, or Cost to compare its API-equivalent budget. Cost estimates retain the dashboard's ~ marker and pricing caveats; see API Cost Accounting.

Groups turns those run-level best observations into a compact experimental summary. Each selected run contributes one best scored candidate, after the time-window filter. The Skill filter can keep all selected runs, any run with an experimental skill, runs with no experimental skill, or runs containing one specific experimental skill found in the report. It uses the same treatment definition as the experimental-skill group presets, so required harness and coordination skills are not listed. Choose mean or median, then optionally split every group by model, coding harness, effort, model and effort, or model and coding harness. Direct labels report the sample size and the aggregate score and budget. Horizontal and vertical min-max ranges remain on by default so a mean cannot hide run-to-run variance or a failed cohort. Candidate number is unavailable in this view because it is not comparable across runs.

For a skill study, select the controlled runs, assign Experimental skill usage, choose Groups, and split by Model + effort. Tokens, active time, elapsed time, and API-equivalent cost can each be used as the budget axis.

See Stop Using Skills: Chart Assets for a worked example using condition means, effort splits, sample sizes, and full ranges.

Use Add text or Add arrow to place an annotation on the report. Drag a text box or arrow to move it. A selected text box exposes a resize handle, and a selected arrow exposes handles for both endpoints. Annotation coordinates are relative to the report surface, so they remain aligned when the output format changes.

Share And Export¶

The toolbar provides these outputs:

Composition state is encoded in the URL fragment. It is not written to the ScoreBench database and the fragment is not sent in HTTP requests. Reloading or sharing the full URL restores display names, colors, run selection, emphasis, chart settings, the label preset, the Groups skill filter, narrative text, text boxes, and arrows.

Sharing Boundary¶

Run filtering in a live Export Studio link is a presentation choice, not an authorization boundary. The generated studio page has the same underlying exercise report data as its public strategy dashboard, even when only two or three runs are visible.

Use the downloaded HTML, SVG, or PNG when the artifact itself must contain only the selected, rendered comparison. These snapshot files do not include the studio's full report payload.

Runtime Cost¶

The report builder generates one export page beside each strategy comparison page. Editing, link serialization, highlighting, and file rendering happen in the browser. No image service, database table, or third-party JavaScript dependency is required.