AI Model Reviewer

GPT-6 Sol in Codex CLI 0.156.1

skills off

← Open in the gallerySame prompt, all models

Zoom, inline player and more ways to view
Poster frame of GPT-6 Sol's page
Open the original page

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).

OKDomino chain physicsmax effortNeutral harness

Wall time 23m 31sCost $3.35 estimated

Review

No verdict yet.

The full review

OK. Finished on its own after 23.5 min.

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, 1,009 characters. Every result for this prompt

Build a single-file Three.js scene with real rigid-body physics (write your own or use a CDN physics lib) of a large domino run: at least 2,000 dominoes in spirals, a staircase, a bridge, splits that branch and rejoin, and a final tower that topples. Include a cinematic follow camera that tracks the leading edge of the wave, a free orbit camera, slow-motion toggle, a reset button, and an IDLE AUTO-PLAY mode that resets and replays the run with a new random layout every time it finishes. Soft shadows, a polished wooden floor, 60 fps target. Output one index.html. Save the main page as index.html in the current directory (plus any local asset files you create), with no build step. You may serve it locally and open it in headless chromium (/usr/bin/chromium, software WebGL, no GPU, no WebGPU) 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. Finish with a short README.md describing the controls.

How it was made

Wall time 23m 31sFirst artifact at 4m 33s23 saved versions

No transcript was delivered with this result.

Cost breakdown

Headline cost $3.35, estimated from the token counts at list price.

Tokens by typeTokens$ per 1MCost
Input (uncached)276$2.00$0.0006
Cache write201,091$2.00$0.4022
Cache read9,306,963$0.20$1.8614
Output108,088$10.00$1.0809
of which reasoning70,839billed as output
Total computed from tokens
$3.3450
Total reported by the harness
none

Computed from harness-reported token counts x list prices. Cache writes priced at the input rate (the price table has no separate cache-write price). No request above 272,000 input tokens (92 checked): standard rates.

Prices: Project price table, 2026-09-25.

Run notes

one prompt, agentic harness (self-review allowed)

  • frozen prompt (written): X-idea prompt queue (frozen in prompts_queue), MR wave 5 Three.js/WebGPU expansion; category threejs; IDLE AUTO-PLAY mode in prompt; engine threejs harness suffix appended; zero results
  • plain CODEX_HOME copy (config.toml only, run work/ trusted; no AGENTS.md/skills/state)
  • Mode: interactive TUI in tmux (160x48), inside bubblewrap sandbox
  • Isolation audit: outside paths seen
  • Renderer: Three.js WebGLRenderer (site/index.html line 550). Three.js r180 and the Rapier physics engine (rapier3d-compat 0.17.3) load from the jsDelivr CDN (import map at line 309, Rapier import at line 362), so the live demo needs network access. No WebGPU needed.
  • No card video (the session capture has only 3 frames): the card uses the poster, the run's own render.png.