Built In Chat.

• Simulation3DElectronicsKael Pro Beta

  Fan Circuit

  Two AA cells, a three-position switch and a small fan on a 3D circuit board, with the current, voltage and speed worked out from the real electrical equations. Written by Kael Pro Beta in one take.

  Try it

  Single HTML file · 1,102 lines · 40 KB · Download

• Game3DSandboxProcedural

  Blockscape

  Explore an endless generated world of forests, deserts, mountains and oceans, then dig and build with ten block types. Sunrises, stars, rippling water and wandering animals, in one file.

  Play it

  Single HTML file · 1,620 lines · 103 KB · Download

• Game3DAI opponents

  Ouroboros

  Steer a snake around a walled arena at sunset, eat glowing orbs and outlast the AI hunters. Three.js, procedural textures and synthesised sound, all in one file.

  Play it

  Single HTML file · 2,725 lines · 90 KB · Download

• Game3DAI opponent

  3D Chess

  Play chess on a rendered black-and-white board against the built-in AI, or switch it off to play a friend. Click a piece to see every move it can make, and watch captured pieces float away to rest.

  Play it

  Single HTML file · 1,916 lines · 65 KB · Download

Just A Chat Window.

Every demo here was made with a single prompt inside a chat interface, with no tools. That makes each one a single take: Kael wrote the whole file as text in the chat, and nobody asked it to re-check or fix anything afterwards. What you try is that file. Each demo’s page says which model and thinking level made it, and gives the exact prompt where we recorded it. If a file was changed after Kael’s reply, that page says so.

One prompt, one take

Each demo is Kael’s first and only reply to a single prompt. Nobody asked it to re-check, fix or improve anything afterwards, and the file is the reply as it came back, except where a demo’s own page says it was changed afterwards.

A chat interface, no tools

Kael had no building tools, no way to run or test its own code, and no browser. The code was written as text in a chat conversation, nothing more.

One file each

Every demo is a single self-contained HTML file, with its styles and script inside it.

Drawn and synthesised in code

There are no image, model or audio files. Textures are drawn on a canvas and any sound is synthesised. The only things fetched are the libraries, loaded from a public CDN.

A Demo Is Not A Benchmark.

These show something Kael wrote, not how often it gets things right, and we aren’t publishing numbers we ran ourselves. Independent results come first; when results exist, we plan to share them on the Kael page.

We’ll add more demos here as we make them. The best test is still your own prompt.