A personal film for every developer.

To close out 2023, Graphite wanted to give developers a look back at their year. We built Year in Code: AI reads your GitHub activity, writes the script, and your browser plays it as a film.

Every film
12 scenes
written by a model for one developer
Storage
100× less
by saving each film as its script

We had built GitHub Wrapped in 2021, which reached 10,000 developers with static images and templated stories. With language models, every film could be written for the one developer watching it.

“In just a few weeks, Rubric went from initial concepts to delivering an engaging AI video experience that reached thousands of users.”
Merrill LutskyCEO, Graphite

The model writes the script

When you sign in, Year in Code reads your GitHub year: commits, pull requests, languages, repositories and stars. A model turns those stats into a one-minute film: 12 scenes of about five seconds each, scripted for you. We asked it for a story with a beginning, a middle and an end, told so the developer watching feels seen.

A scene from a Year in Code film: “Dexter, you made 742 contributions this year” over the number in 3D pixel type

Our first tests gave the model full creative freedom, and the films weren’t good enough. So we built a bank of animated scenes, some of them in 3D: a planet, a flashback, your top languages, the people you worked with. The model picks the scenes, puts them in order, and writes every line on screen.

Each scene declares the data it needs, like the planet an intro opens on, and every script is checked against those declarations before it plays. A scene never plays without its data.

Title card: Dexter’s 2023 Year in Code, by Graphite, over a planetA quiet winter, then a November to remember: contributions month by monthBuilding Rubric Labs alongside Sarim and Ted, with their avatarsThe closing summary: 276 commits, 742 contributions, 31 pull requests, and his top repositories

Save the script, not the video

Year in Code stores each film as its script, and your browser plays the scenes live from it. That cut storage and bandwidth by about 100× and kept every film interactive. Each film also has its own link, so a friend who opens it watches the same film, played from the same script.

Year in Code: save the script, not the videoA developer's GitHub stats go to a model, which writes a twelve-scene script. Only the script is stored, about 100 times smaller than video, and the browser plays it live. An MP4 is rendered only when someone downloads their film.Your statsModelScript12 scenesStoredAbout 100× smaller than videoPlays liveMP4Only on download
From GitHub stats to a film in your browser

Rendering an MP4 is the most expensive step, so it only happens when someone downloads their film to share it, and only once per person.

Open source

Year in Code asks for the fewest GitHub permissions it needs, and none that reach your code. It’s also open source, so any developer can check exactly what it reads, and see how the scenes and the script fit together.

Keep reading

An agent that books your meetings by email.

Work with us

Want outcomes like this in your product? Let's talk.

Rubric Labs is a small team of founder-level engineers with a research lab. We join your team, learn your problem, and build it with you all the way to production.

Book a call1 slot open in Q4 2026