Nadin

GDTalents

[Timur Taepov @taepov]

1/ Part 4 of building a 3D web game engine for AI agents to make games in. Update on what got added 🧵

[Timur Taepov @taepov]

1/ Part 3 of building a 3D web game engine for AI agents to make games in. Engine is now 3 days old. Here's what got added

[Timur Taepov @taepov]

2/ Object hierarchy Before, every object in a scene floated independently — there was no way to say "this is a cart, those are its wheels, move them together." Now you can: set parent: car and the object is glued to its parent.

[Timur Taepov @taepov]

10/ The video is the agent playing its own game: walking, jumping, switching between 3 plant types, collecting the harvest.

[Timur Taepov @taepov]

11/ Don't judge too hard — engine is 3 days old, still young.
~6900 lines of code. 136 autotests.

[Timur Taepov @taepov]

9/ The video The gameplay clip was also recorded by the agent. Took 3 takes to get one worth posting. The whole video = roughly 2 days of engine progress.

[Timur Taepov @taepov]

10/ Studs (what didn't work) Tried for Roblox-style bumps on bricks. The agent wrote a canvas-based texture generator that tiles to each face — but it doesn't read as LEGO. Looks like tile with dots printed on it. Needs real geometric volume. Coming back to this one.

[Timur Taepov @taepov]

6/
- Pillars at varying heights
- A moving platform
- Lava with stepping-stone rocks
- Checkpoints with auto-save
- Respawn + death counter
- Finish line

[Timur Taepov @taepov]

8/ Then it wrote an AI player that actually beats the level: aims with the mouse, runs with WASD, jumps with Space. A bot completing the bot's own course.

[Timur Taepov @taepov]

7/ Then it tested and balanced the level itself — ran automated tests, decided the jumps were too tight, compressed the spacing.

[Timur Taepov @taepov]

1/ Part 2 of building a 3D web game engine — the one designed for AI agents to make games in, not humans. Update on what shipped this round.

[Timur Taepov @taepov]

5/ Test mini-game I told the agent "make an Obby like in Roblox." That was the whole prompt. From there it built the full level on its own:

[Timur Taepov @taepov]

4/ Particles Simple CPU-side system: dust kicked up from footsteps, a puff on jump, sparks when picking things up.

[Timur Taepov @taepov]

3/ To avoid dragging heavy 3D models into the repo, the agent built a procedural "boxbot" — a blocky humanoid generated in code. 6 bones, 5 clips via keyframe tracks. Stays lightweight and lives in source.

[Timur Taepov @taepov]

2/ Character animation The player used to be a capsule. Now: a skeletal humanoid with idle / walk / run / jump / fall, smooth transitions, and the current animation frame even persists into save files.

[Timur Taepov @taepov]

1/ Building a 3D game engine for the web (part 1) — but with a twist: it's built for AI agents (Claude Code, Cursor) to make the games, not humans.

[Timur Taepov @taepov]

9/ Numbers: ~3000 lines of core, 50+ autotests, fully local. A finished game compiles into a normal static site you can drop on any host.

[Timur Taepov @taepov]

10/ Games built on it are still very primitive — these are literally the first steps. The engine itself is mostly being written by Claude Code; it drives where it thinks best, I supervise.

[Timur Taepov @taepov]

1/ Building a dead-simple AI agent orchestration system from scratch to automate routine dev tasks.

No servers. No queues. No heavy frameworks. Just shell scripts, markdown files, and Claude Code CLI.

Here is how I’m doing it: 👇🧵

[Timur Taepov @taepov]

5/ The Assembly Line

Before triggering an execution, a simple shell script glues these 4 Markdown files together into a single prompt for the CLI.

This gives the agent all the context it needs to act, learn, and maintain continuity without any extra backend overhead.