gpt-oss-120b in a raw API call
raw API baseline
Zoom, inline player and more ways to view
The model's own page, run in a sandboxed frame only when you ask (a page that needs its own origin opens in a new tab on a separate demo site). Phones get a full-screen player capped at 1.5x pixel density (2x on larger screens) so it stays smooth; the original page runs uncapped. It starts in its auto-tour (T switches to play mode on a keyboard).
The model's code errors on load: Failed to resolve module specifier "three". Relative references must start with either "/", "./", or "../".
Wall time 12 sCost not recorded: the run's token counts were never reported, so there is no estimate
Review
No verdict yet.
Scores
AI judge
Not scored
No rubric for this prompt
Visitor votes and reviewer grades are not available yet.
- AI judge
- AI judge: the test runner (model claude-opus-5-5), scoring by visual review of the 1600 px render against the pre-registered rubric. No AI-judge score exists for this result: there is no rubric for this prompt, so no score is shown and none is made up.
- Visitors
- Public voting with a blind reveal is coming: you score the output first, then see the other scores.
- Reviewer
- The reviewer's own grade appears here once it is added.
Scores compare results for the same prompt only. AI-judge boards rank runs within one prompt, equal totals sharing a rank; scores from different prompts are never averaged.
Downloads
Files actually published for this run. Original output, site-made previews and post-run conversions are labelled separately.
The exact prompt
as run, 806 characters. Every result for this prompt
Build a Three.js scene: A log cabin on a mountainside in a blizzard: dense snow particles driven by gusting wind, snow gradually accumulating on the roof and ground, warm light glowing from the windows and chimney smoke torn sideways. Toggle between blizzard and calm snowfall; the camera circles slowly at a distance. Everything is built in code from Three.js geometry, materials and shaders; no external models or textures. Build it as index.html (plus any local asset files you create) in the current directory. Three.js may load from a pinned CDN. You may serve it locally and open it in headless chromium (/usr/bin/chromium, software WebGL, no GPU) to screenshot and inspect your own output, and iterate on your own before finishing. Close any browser you open as soon as you've taken your screenshot.
How it was made
Step by step
The prompt, every agent turn and tool call (tool name and a one-line summary; inputs and outputs are not shown), then the final message. The full machine-format transcript is published as a scrubbed download.
Show all 2 steps
Loading the timeline…
Download the full transcript raw API response, 20 KB. Scrubbed: anything that looks like a key, token, e-mail address or phone number is replaced, and account details and the test machine's file paths are removed.
Cost breakdown
No cost figure: the run's tokens were never reported, so there is nothing to estimate from.
| Tokens by type | Tokens | $ per 1M | Cost |
|---|---|---|---|
| Input (uncached) | 234 | n/a | n/a |
| Cache write | 0 | n/a | n/a |
| Cache read | 0 | n/a | n/a |
| Output | 19,089 | n/a | n/a |
- Total computed from tokens
- unknown
- Total reported by the harness
- none