- Who it helps
- Game prototypers and developers investigating open-model coding demonstrations.
- Availability
- The public artifact account uses Bonsai 2 27B in a quantized format with an agent runner. It reports H200 and RTX PRO 6000 hardware, which does not establish ordinary-laptop performance.
Look at the revisions
Compare a prompt with the following generated page and trace. That reveals how much was produced, corrected or left incomplete at each stage, beyond the final clip.
Keep the execution risk explicit
The documented runner uses a permissive mode as the local user. Reading the artifacts is a useful first step; adopting that execution mode would require a separate isolation and permissions decision.
What you can do
- Inspect the saved prompt and output sequence before considering a local reproduction. Open reference ↗
Where the evidence stops
The demo and third-party code were not run. Its timing is a creator report tied to named hardware; the publication date was not established.
Sources read. Public source material was read October 17, 2026 UTC. No model inference or third-party project was executed.
Sources & further reading
GitHub · demonstration
Bonsai game-building demo artifacts ↗
Primary artifact log includes prompts, traces, hardware and generated pages for a skateboard game exercise.
PrismML · page checked 2026-10-17
Coverage note: The cited bundle covers the available primary explanation. Matching original X posts, a complete video comparison and independent execution evidence were unavailable.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
PrismML’s Bonsai demo documents a generated browser skateboard game with saved prompts, agent traces and intermediate pages. Those artifacts make the creation process easier to examine.