oneshotlm
Compare all models on this prompt →

3D solar system · gpt-5.1-codex-mini

Using the pre-provided three.min.js (global THREE), build a 3D solar system with the sun and orbiting planets at varied speeds and sizes, orbit-drag camera controls, and a starfield.

⛨ sandboxed Open in new tab ↗
transcript · 8 messages
user

Using the pre-provided three.min.js (global THREE), build a 3D solar system with the sun and orbiting planets at varied speeds and sizes, orbit-drag camera controls, and a starfield.

assistant
bash {"command":"pwd"}
toolResult

/tmp/ws

assistant
bash {"command":"ls"}
toolResult

three.min.js

assistant
thinking
**Planning a solar system model**

I’m working on creating an index.html single-page application that includes inline styles and scripts. My focus is on the solar system with the sun and planets, taking into account their orbits, sizes, and speeds. I need to determine if I should implement custom camera controls for orbiting or use the built-in THREE.OrbitControls. I must also ensure there's a starfield background and follow the instruction to avoid using any external files. Alright, let’s lay out the structure!**Implementing starfield and camera controls**

I’m adding a starfield by creating geometry with random positions. For camera controls, I’ll set up a simple implementation where the camera orbits around the center on mouse drag and possibly supports zooming with the wheel. I plan to use spherical coordinates for the camera and update them based on mouse movements. For the planets, I’ll create an array with data for each one, including size, distance, and speed. Plus, I need to add their orbits, maybe with dashed lines or circles. Let’s keep it organized!**Finalizing the implementation steps**

I need to make sure I’m using the functions from three.min.js properly. I’m also thinking it might be helpful to include some text instructions for clarity. To move forward, I’ll generate the HTML string for the final index. It seems I’ll need to use the editor to create the file, so I’ll proceed with writing the content. Let’s make sure everything is well-organized and clear for the user!**Creating the pseudo HTML structure**

I'm working on a basic structure for my solar system project in HTML. I’ll set up the doctype, along with the head, where I’ll include the title and some essential CSS styles for the body and info section. The body will contain a div for user instructions, and I’ll link the three.min.js script. 

The script section will handle setting up the renderer and scene, with lighting and the sun mesh. Then, I’ll start creating the planets and their orbit paths. Let's get everything lined up!**Setting up the starfield and controls**

I'm planning to create a starfield by constructing a BufferGeometry that will hold a float32 array for around 1,000 stars, using PointsMaterial for the appearance. For the camera controls, I’ll track drag actions with an `isDragging` variable and previous mouse position. 

I’ll set up event listeners for pointer events to handle mouse interactions, and make adjustments using the mouse wheel to control the radius. I also want to implement animation for the planet and sun rotations, include resize watchers, and finalize the instructions. Let's get those files created!
write index.html (7141 bytes)
toolResult

Successfully wrote 7141 bytes to index.html

assistant

Built a self-contained `index.html` featuring a Three.js solar system with a sun, planets, orbit visuals, starfield, and orbit-style camera controls, all using the provided `three.min.js`.

TAKE IT TO CODE

A single self-contained HTML file — copy it and open in any browser, or reuse the prompt with your own pi-agent run.

RUN

modelgpt-5.1-codex-mini
vendorOpenAI
harnesspi-agent
generated2026-08-01

EVALUATION

4/5 working

Solar system with sun, orbiting planets of varied sizes/speeds, rings, orbit lines and starfield; animates continuously, but drag/click camera control seems weak.

Vision grade · anthropic/claude-sonnet-5

MEASUREMENTS

Raw readings from the capture, not a verdict — the grade above is the only judgement. Percentages are how much of the screen changed; the measure under-reports sparse motion on a dark background.

idle motion4.6%
on click4.3%
on drag4.1%
on wheel4.8%
on enter + space11.3%
on arrow keys4.0%
on w/a/s/d10.0%
frame spread35.5 / 255
console errors0
js errors none

METRICS

runtime30.8s
tokens in7.4k
tokens out3.5k
cached4.6k
cost / run$0.0079