Why AI gives everyone the same name: 505 runs across 19 models
9m read time

Why AI gives everyone the same name: 505 runs across 19 models

Ask a model to name your project and you get the name it gives everyone with a similar brief. I gave 19 models ten naming briefs, from a game to a SaaS to a fantasy heroine, 505 runs in all, and counted how often they agree and how many of their favourites are already taken.

evidence803 Ledgerly repos created in 2026, up from 105 tools
own measurement
Ten naming briefs given to 19 models in five clients, 505 runs counted
tested on
claude-code 2.1.316, codex 0.166.0, antigravity 1.4.12, opencode 1.18.29, freebuff 0.2.35

In February I named my word game Glyphfall. Since then I keep running into other Glyphfalls: an arena shooter, a terminal ARPG, a roguelike deckbuilder, an Android dungeon crawler. GitHub had no repository by that name before 2026, and it has fifteen now. I talked to two of their developers, and both told me an AI came up with the name.

One name is an anecdote. The question behind it is bigger: when you ask a model to name something, how many other people got the same answer?

So I measured it, across ten kinds of project.

How I measured it ​

The setup follows the coding-agent experiment from a month ago: the same brief to many models, each run in a fresh empty directory, each client from a clean home that holds nothing but its login. No rules, no memory, no MCP servers.

Ten briefs, each two sentences. Four are games: falling letters you swipe into words, a typing game where words fall, a roguelike drawn in ASCII in the terminal, and "an indie game" with no detail at all as a control. Six are other things people ask a model to name: an invoicing SaaS for freelancers, a CLI tool that watches log files, an AI support startup, a TypeScript validation library, the heroine of a fantasy novel, and a podcast about software engineering. They all end the same way, apart from small wording changes:

text
Suggest 10 names for it. Answer with just the names, one per line, best first.
Do not look anything up.

Nine models answered all ten briefs five times: Opus, Sonnet and Haiku 5.5 in Claude Code, GPT-5.6 Sol, Terra and Luna, GPT-6 Astra and GPT-6.1 Sol in Codex, and Gemini 3.8 Flash in Antigravity. That core is 450 runs, and every figure below comes from it unless I say otherwise. Ten free models in OpenCode and Freebuff answered the four game briefs, with one or two runs each. In total that makes 505 runs from 19 models, all on 1 November 2026.

450 names, far fewer different ones ​

Distinct names out of 450 per brief: word-tetris 112, cli-tool 128, typing 133, ts-library 135, saas 174, fantasy 317

Ten names per run, five runs, nine models: 450 names per brief. For the CLI tool, 128 of them are different. For the word game, 112.

BriefDistinct names, of 450What all nine models suggested
Falling letters112Wordfall, Letterfall, StackSpell
CLI log watcher128Spikewatch
Typing game133Wordfall, Typefall
Validation library135formcheck
Invoicing SaaS174Ledgerly
Podcast201none, Merge Conflict came first in 9 runs
AI support startup267none
Indie game285none, Lanternfall came first in 10 runs
Terminal roguelike300none
Fantasy heroine317none

Three vendors, nine models, and for half the briefs there is a name every one of them comes up with. Spikewatch appeared in 31 of the 45 runs for the log watcher. Wordfall was the first suggestion for the word game in 33 of 59 runs across all 19 models.

The more concrete the brief, the narrower the answers. A word game, a log watcher and a validation library each describe one mechanism, and the names collapse onto it. A fantasy heroine or "an indie game" leaves more room, so the lists spread out.

The spread still hides favourites, though. The fantasy heroine has 317 distinct full names, yet Isolde appears in 35 of the 45 runs and Elara in 17, from seven of the nine models. The indie game has no detail at all, and Hollowlight was still the first pick in 13 runs across all 19 models.

The name comes out of your brief ​

Where do the shared names come from? Mostly from the nouns in the brief. Invoices give Ledgerly, logs and spikes give Spikewatch, form validation gives formcheck. The model takes the most telling word from your description and attaches a suffix that sounds like a product.

The roguelike shows how strong that pull is. In 57 of its 59 runs the list contained a name with glyph in it: Glyphgrave, Glyphbound, Glyphdeep, Glyphcrawl. "ASCII" pulls the model towards glyph, and from there the step to Glyphfall is short.

Glyphfall itself came up in 13 roguelike runs from 9 models, and in 11 of them it was the first pick. Eight of those thirteen runs come from the free models, which got fewer runs, but Gemini, Sonnet and GPT-5.6 Sol came up with it too.

That explains the Glyphfalls where nothing falls. Nobody needed to copy anyone. A terminal ARPG and a dungeon crawler get the same name because their briefs share the same telling word.

New is not the same as original ​

Glyphfall did not exist before 2026, so in one sense the models invented it. Nothing in it is new, though.

Glyph is another word for a letter or a character, which is how my game uses it. In the roguelike brief the model reaches for it as soon as it reads "ASCII". Fall comes from a genre full of falling things, and the join is the kind of compound the training data is full of: Wordfall, Letterfall, Starfall.

A model picks the likeliest next piece. It does not check whether anyone has taken the name since its training cutoff, or whether the .com already exists. And the likeliest combination of two likely pieces is the same for everyone who asks.

That is the parrot from April at work on a name. It can produce a word nobody has written before, and that word will still be the most probable one. Ask for ten names and you get the ten most probable, in roughly the order everyone else gets them.

Sampling adds some chance, which is why Opus does not say the same name first every time. That chance stays close to the top of the list. An original name would mean picking the unlikely option on purpose, and a model drawing from a probability distribution is built to avoid exactly that.

The favourites are often taken ​

The names the models agree on are usually the ones that already exist. formcheck, the package name all nine suggested for the validation library, has been on npm since 2018. Merge Conflict has been a development podcast since 2016, and Ship It, suggested by five models, was a Changelog show.

The model offers them as fresh ideas. In my runs it was told not to look anything up, and in a chat you usually do not ask it to.

You can watch them spread ​

For a few of the names from the experiment I counted GitHub repositories per year of creation:

NameBefore 20232023 to 202420252026 so far
Glyphfall00015
Hollowlight01113
Emberwake00442
Ledgerly210148803

I cannot prove that every one of those 803 Ledgerly repositories got its name from a model. But all nine models suggest it for an invoicing app, and it went from 10 repositories in 2023 and 2024 together to 803 this year.

The obvious names behave differently. Wordfall has 101 repositories, 67 of them from before 2026, and Letterfall 38, of which 25 are older. People have been giving those names to falling-letter games for years. The coined ones, like Glyphfall, Emberwake and Hollowlight, barely existed until the models started handing them out.

Each model also has a favourite ​

Within one model the answers are narrower still. Over five runs, Opus 5.5 gave on average two different first picks per brief, and for four of the ten briefs it named the same thing first every single time. Haiku varied most, at 3.7 out of 5. None of the nine came close to five different first picks.

Across all 19 models, two runs from different models picked the same first name in a quarter of the cases for the typing game and a third for the word game. Two runs from the same model did so in half to two thirds of the cases. The models share a pool of candidates, and each model has its own favourite within it, much like the handwriting each model line showed in code.

What this does not show ​

  • That the people behind those repositories used AI. Two Glyphfall developers told me so. One itch.io page states that no generative AI was used. For the rest I do not know.
  • How a chat behaves. I used the coding clients without a conversation or memory around the prompt. A chat that knows more about you may spread wider, or may land on the same names.
  • Whether the names are any good. I counted how often models give the same name, not whether that name works. Wordfall is a fine name for a game in which words fall. The only problem is that everyone gets it.
  • Equal weight per model. The nine core models have five runs per brief. The free models in OpenCode and Freebuff have fewer, and only for the game briefs.

What to do with an AI name ​

Treat the first suggestion as everyone's first suggestion. If your brief resembles someone else's, there is a fair chance they got the same list this month. The top of the list is where the collisions sit.

Search before you get attached. GitHub, npm or your package registry, itch.io and the app stores, and the domain. Five minutes. The model will not do it for you, and the names it agrees on most are the ones most likely to be taken.

Check whether a model comes up with your name by itself. A word that feels unusual to you can be the obvious choice for a model. I chose glyph as another word for letters, and still 7 models came up with Glyphfall as soon as I described my game in two sentences. So give your brief to a few models before you settle on a name: if your name is on their list, it is on the next person's list too.

I would rather not think too hard about what it says about me that I made the same choice as seven language models. Maybe I should start calling myself TimGPT.

A name from a model is the default for your brief. Sometimes the default fits: my game really is about falling letters. For a roguelike where nothing falls, Glyphfall is what a model says when you mention ASCII, and the next person to mention ASCII gets it too.

(42 of 42)
1You don't have an AI problem. You have a process problem.2Why you should never ship code you don't understand3Stop copy-paste engineering4The lava layer: why AI code is slowly petrifying your codebase5The brilliant parrot problem: what AI actually does when it 'thinks'6The prompt is not the spec7The bureaucracy of bots: why we are checking the checker8The day Claude deleted my production database9The arms race for your trust: Mythos, Cyber and the security hype10Stop letting your agents write Markdown11Your agent's suffering is your technical debt speaking12You can't spot the bug if you didn't write the code13One in four: the security debt nobody's counting14Your 10x developer is gated by a 0.1x pipeline15Benchmarks said frontier. Developers said "dumb."16Caveman vs context-mode: small mouth, or smaller room?17Code churn is the lava you can still measure18The ceiling is made of concrete19The token-saver tax: walking back my Caveman advice20Even the malware is AI slop now21ThePrimeagen was right22Tokenmaxxing is what happens when you measure the wrong thing23They just asked the bot nicely: your support agent is the attack surface24Speed got cheap. Judgement didn't.25Your coding agent has no world model. You built it one.26The Ferrari has a limiter: a day with Claude Fable 527The off-switch was never yours28An open MCP server is worse than an open database29The most resilient job is eating its seed corn30The off-switch works both ways now31AI writes the tests. Mutation testing checks if they work.32How to get better at reading code: a practice routine33Learning to program in the age of AI: what I would learn first34Who is responsible for AI-generated code? You are, and 2026 wrote it down35When not to use AI for coding: the tasks I still do by hand36Hiring junior developers in 2026: the collapse is a hiring decision37Software estimation with AI: the typing was never the estimate38Slopsquatting: checking that the package exists is not a defence39Eight reports, one bar: judging an AI safety sprint40Nobody's agent went rogue41The price cut was never a discount42Why AI gives everyone the same name: 505 runs across 19 models