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: Cannot access 'camAnim' before initialization
Wall time 5.5 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, 2,244 characters. Every result for this prompt
Build a Three.js scene: An animated, step-by-step 3D explainer titled "Automating Your Raised Garden Beds". A small backyard with two or three wooden raised beds of soil sits on a lawn beside a house wall with an outdoor tap. The tutorial plays through clear steps, each with a short on-screen caption (step number, title and one or two sentences) and its own automatic camera move to frame what is being explained: 1) the water source: the outdoor tap with a backflow preventer and a pressure regulator; 2) the timer/controller mounted by the tap, with a small display; 3) the main supply line running to the beds; 4) drip lines laid along each bed, with animated water droplets dripping from the emitters; 5) soil moisture sensors pushed into the soil, showing a live moisture reading that rises as the drip runs; 6) a small solar panel on a stake that powers the controller, with a subtle energy-flow animation; 7) the finished system running on its own over a day-night cycle while the plants (lettuce, tomatoes, herbs) visibly grow from seedlings to full size. Each new component animates into place (drops in, slides or unrolls) when its step begins, and highlighted parts glow gently. Controls: Play/Pause, Previous and Next step buttons, and a row of step dots showing progress; it auto-advances when playing. OrbitControls let the viewer look around, and the tour camera resumes on the next step. Everything is built in code from Three.js geometry, materials and shaders; no external models, textures or fonts. The scene must visibly animate from the moment it loads and run in a browser with software WebGL (no GPU). Deliver ONE self-contained HTML file; load Three.js only through an import map from https://cdn.jsdelivr.net/npm/three@0.170.0/build/three.module.js (addons from https://cdn.jsdelivr.net/npm/three@0.170.0/examples/jsm/), with no other external requests (no image, texture, model, font or audio files): build every shape and texture in code. It must work when opened directly from disk in a current desktop or mobile browser, fit the window responsively, and run without console errors. Output ONLY the complete HTML file, starting with <!DOCTYPE html> and ending with </html>, with no explanation or markdown fences.
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, 17 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) | 561 | n/a | n/a |
| Cache write | 0 | n/a | n/a |
| Cache read | 0 | n/a | n/a |
| Output | 12,414 | n/a | n/a |
- Total computed from tokens
- unknown
- Total reported by the harness
- none