GPT-6 Astra in Codex CLI 0.156.1
skills off
Zoom, inline player and more ways to view
Wall time 11m 38sCost $2.20 estimated
Review
The cleanest result on a home harness: an open gap between the grips and no dark slab, in a flatter vector look. At $2.20 and 11.6 minutes it is the best result per dollar among the strong results.
Verdict by reviewer.
The full review
OK. Finished on its own (task_complete) after 11m37s of agent time.
Earlier verdict by test runner
Cleanest controller of the test. Correct silhouette with a real open gap between the grips (no dark slab — the flaw both Opus runs share), clean 4-piece D-pad, outline-style face symbols in the right colours, black core with grille, textured stick rings, blue light bars, mute bar + mic icon, Create/Options with icons, triggers peeking over the top. Weaknesses: flatter "vector product-shot" look with less material texture than Claude Code/Opus; PS logo is a downloaded path; touchpad is plain. At $2.20 and 11.6 min it beats Claude Code/Opus ($12.80, 57 min) on result per dollar and arguably on the result itself.
Kept as written in the result folder; the verdict above replaces it.
Bugs
- Flatter vector look, less material texture
- Touchpad plain
- PS logo is a downloaded path, not model-drawn
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
agentic harness (save the file; self-render allowed), 2,074 characters. Every result for this prompt
Create a single self-contained SVG illustration of the Sony PS5 Pro DualSense wireless controller at MAXIMUM fidelity. This is a showcase piece: take your time to plan the geometry carefully before writing it. Requirements: 1) Accurate DualSense silhouette and proportions: a wide body with the large, wide touchpad spanning the top centre, two flared, rounded grips sweeping down and outward, and a perfectly symmetrical left/right layout. White outer shell with the black central core section. 2) Face buttons on the right in the classic diamond: triangle (top), circle (right), cross (bottom), square (left), each drawn as clean PlayStation symbols in their real colours (green triangle, red circle, blue cross, pink square) in the modern outline style on light buttons, with subtle bevels. 3) D-pad on the left as FOUR separate arrow-shaped directional buttons (up, down, left, right), not a single cross. 4) Two black analog sticks with concave tops and a textured grip ring (fine radial or dotted texture) and shading. 5) The PlayStation logo button centred below the touchpad between the sticks, the small mic mute button with its orange-tinted indicator line just below it, the Create button (left) and Options button (right) flanking the touchpad. 6) The blue light-bar glow running along both side edges of the touchpad, with a soft bloom. Speaker grille holes on the black core. 7) Realistic product-render shading: gradients, specular highlights, soft ambient occlusion, a contact shadow beneath the controller. 8) A clean dark studio background with a subtle radial vignette. Front-on hero shot, centred and filling the frame well. Use viewBox="0 0 1600 1100" with width="1600" height="1100". No external assets, no raster images, no fonts, no scripts. Output ONLY the complete SVG code, starting with <svg and ending with </svg>, with no explanation or markdown fences. Save it as controller.svg in the current directory. You may render and inspect your own output (headless chromium is available at /usr/bin/chromium) and iterate on your own before finishing.
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 transcript is 4.3 MB; it is published as a scrubbed, compressed download rather than shown on the page.
Show all 24 steps
Loading the timeline…
Download the full transcript Codex CLI rollout JSONL, 49 KB, gzip. 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
Headline cost $2.20, estimated from the token counts at list price.
| Tokens by type | Tokens | $ per 1M | Cost |
|---|---|---|---|
| Input (uncached) | 33 | $10.00 | $0.0003 |
| Cache write | 40,308 | $10.00 | $0.4031 |
| Cache read | 226,084 | $1.00 | $0.2261 |
| Output | 31,470 | $50.00 | $1.5735 |
| of which reasoning | 7,859 | billed as output |
- Total computed from tokens
- $2.2030
- Total reported by the harness
- none
computed from harness-reported token counts x list prices. Tokens from Codex rollout token_count (input_tokens includes cached + cache_write; uncached = remainder). Codex prints no dollar figure. Cache-write priced at input rate (not published).
Prices: project price table 2026-09-22 (OpenAI Standard tier, prompts <=272K); cache write not published, priced at input rate, 2026-09-23.
Run notes
- Fetched the official playstation.com DualSense product page and product PNG as visual reference (viewed it).
- Downloaded the simple-icons PlayStation logo SVG path and embedded it (so the PS logo is a sourced path, not model-drawn).
- Wrote a Python builder that emits the SVG; rendered in headless Chromium; viewed; patched gradients/offset; re-rendered.
- Mode: interactive TUI in tmux 160x48
- Self review: rendered with chromium and viewed its own render twice (preview + final), applied 2 small patches
- Wall time note: agent working time from Codex task_complete (11m37s); runner detected completion late (850 s) due to a session-lookup bug on our side, not harness time
- Context setting: Codex default (258K window reported by /status)
- Isolation: none (run began before §4 isolation rule); audit below
- Isolation audit: clean: only /tmp files it created itself (references, builder, previews) plus `rg --files -g AGENTS.md /tmp` which lists only AGENTS.md files; no access to other runs (/tmp/hx_claude_code, /tmp/work, the project files) — no contamination