A demo Andrej Karpathy posted over the weekend stuck with me. He gave Opus 5 a million-token context and the first paragraph of The Lord of the Rings, and asked for a procedural 3D rendering of the scene in Three.js. The model worked alone for about two hours, wrote 5,500 lines, and coordinated polygon placement, camera paths, and animation on its own. Total cost: about $10. The result is faster to watch than to describe.
Most reactions read it as the next step past "draw a pelican SVG" benchmarks. Something else looked bigger to me. What changed isn't the model's artistry. It's the unit of delegation.
The unit of delegation changed
Until now, the work we handed agents came in prompt-sized pieces. One function, one bug, one file. Anything bigger, we decomposed ourselves. The reason was simple: with a small context, the early parts of a long job slide out of view, and coherence goes with them.
A million tokens erases that premise. Everything the model wrote and tried across a two-hour session stays in view. When the desk is big enough, there is no reason to hand work over in slices. Delegation moves from the task to the session.
That is the difference between a function call and a work session. The first, we decompose and supervise. The second, we hand over material and intent, and receive a result. Karpathy's entire contribution was picking the paragraph and watching the output two hours later.
Where the builder's work moves
When execution costs $10 and two hours, execution is no longer the bottleneck. Two things remain.
On the way in: the brief. What goes into the context. Karpathy's input was one paragraph, but choosing it was the design act. Translated to our work, it becomes choosing which spec, brand guide, reference, or codebase goes in whole — and what stays out.
On the way out: judgment. By what standard do you accept the result? Reviewing 5,500 lines one by one doesn't match session-sized delegation. Instead, you define "done" before the run, then judge the output against that bar.
Breaking work into pieces and supervising the process was the senior skill for a long time. Its value is falling; choosing the material and setting the bar are rising. An uncomfortable shift, but the direction looks clear.
How far does this carry
Fairness requires a line. Three things this demo does not prove: there is no maintenance, no correctness constraint, no user. A clumsy render costs a little enjoyment and hurts nobody.
So the litmus is one line: is the output for viewing, or for operating? Mockups, prototypes, exploration, and demos can afford to be wrong. Going from spec to demo in one shot may already be faster this way. Software that operates, where a mistake reaches users and tomorrow brings maintenance, is still a different game. Nothing in this demo shows that the output of a two-hour autonomous run belongs in production as-is.
Try this week
Instead of admiring it, design one experiment. Pick something in your own domain that fits "whole material in, half a day of autonomy."
- Feed the full product spec and brand guide, ask for a demo in one shot
- Feed the whole codebase, ask for a migration draft
- Feed all the docs, ask for an onboarding guide
Two conditions are enough: the output must live where wrong is affordable, and the cost cap is set in advance. Ten to twenty dollars will tell you whether the unit of delegation has changed for your work too.
Top comments (0)