A sentence in the chat, and blocks in the ground.

"Build a road to Ash's house." "Go and get me some iron." "Make the wheat farm bigger." Start with what you want rather than a block ID. Say it the way you would to a mate who happens to be very good at Minecraft, and Cog works out the rest.

1. 01

   You ask for something

   "Cut a canyon through here." "I want to get across the lake." "Put a secret door in this wall." Type it the way you would say it. There is nothing to learn first.

2. 02

   Cog fills in the blanks

   You did not say how wide, what out of, or which way round the creek. Cog looks at what is actually there, the hill, the water, the trees, and decides.

3. 03

   You watch it go up

   Once a design is ready, blocks go down while you stand there. In creative, a keep rises in front of you. In survival, Cog walks over and digs at the pace anyone at a keyboard digs.

4. 04

   Cog measures what they built

   When the last block lands, they read the finished thing back out of the world. Is the road one connected piece? Does the stair rise one block a step? Did the wheel turn when the lever went on?

5. 05

   Cog tells you the numbers

   You get the counts and checks in plain words, including anything they could not finish. If something needs another look, ask a follow-up.

A spiral staircase needs to rise one block a step. A hidden door needs to open and close. For supported shapes and circuits, Cog starts with builders that have already been tested, then checks what they placed in your world.

Those reusable pieces handle the geometry and wiring, leaving Cog to decide how they fit your request. World conditions and later changes can still cause problems, and the measurements give Cog something concrete to check, explain and, where possible, fix.

Ask for a road and they have a road-builder. Ask for a stone dragon curled round an outcrop and there is no dragon-builder, and there never will be. Nobody can build every idea a nine-year-old is going to have in advance. So Cog designs it instead, writing the shape down as solids: ellipsoids for the coiled body, cones for the horns, slabs for the folded wings.

Then Cog looks at the drawing from the front, the side, above, and in a cut straight through the middle, and tells themselves what is wrong with it. The wings are stubs. The head is too small for the body. It is in three pieces instead of one. They fix those and look again. Thinking is the slow part, so the first round is three separate attempts at once, and the soundest goes forward. All of this happens before a single block goes down in your world.

It is what a person does with a sketch. Cog’s first rocket had its fins fused into one solid skirt; by the fourth draft they were separate blades with daylight between them, and the rocket had grown an engine bell with a glow inside it. Nobody told Cog to fix the fins. They looked, and did not like them either.

Our lighthouse demonstration took minutes to design and seconds to place. Keeping the drawing lets Cog reuse it when somebody asks for “another one of those, over by the lake”. That skips the original design work, though the new request still uses AI credits and needs a suitable place to build.

Cog also remembers where things went. Ask for something on a spot that is already taken and they say so ("there is already a SpongeBob house there, do you want it beside it, or should I take that one down?") rather than quietly building on the roof.

A goal that counts. A timer that runs. A pad that hands you snowballs the moment you stand on it. None of that is a shape you can pile up out of blocks. It is a rule, so Cog writes the rule.

Ask for soccer and Cog lays the pitch, works out the rules that make it a game, and puts them into the server you are standing in, without a restart and without anyone being kicked off or downloading anything. Loading finished rules can be quick; designing and checking a new game takes longer. The examples are recorded runs, not a promised response time.

A rule that quietly never fires looks exactly like a rule that works, so Cog then triggers every one of them on purpose and reads the result back before telling you to go and play.

Supported game rules can load while your friends keep playing on the ordinary Java client. Server updates are separate and may need a restart; not every change can happen in a running world.

1. Your house
2. Cobble, three wide
3. Bridge the creek
4. Grade the rise
5. Torches for the dark
6. Ash's house

Cog works out where both houses are, picks a route, a width and a material, and starts laying cobblestone three wide with a fence down one side. They bridge the creek instead of wading it, grade the shoulder up the rise instead of leaving a cliff face, and drop torches in as they go so nothing spawns on it after dark. Watch the whole thing, or go and make a sandwich and come back to a road.

Then Cog walks it end to end before saying it is finished, so you get a road you can follow rather than a line of blocks that looks like one from the air.