A domain name became this week’s drama.
According to TechCrunch, the internet is convinced that Elon Musk’s xAI trolled OpenAI’s Dots launch by buying the domain name dots.com. That’s the whole story, and it’s enough. Nobody has confirmed whether it was a prank or a routine domain acquisition, and honestly, the ambiguity is doing more work than a confirmed answer ever could. A registration record is a Rorschach test. Everyone sees the feud they already believed in.
I build bots for a living, which means I spend an unglamorous amount of time on naming things. Not brand naming with mood boards and font pairings. The boring kind: what do I call this agent in the tool registry, what’s the package name, what string shows up in the logs at 2am when something loops forever. So my reaction to the dots.com story wasn’t “who won.” It was a small wince of recognition. Generic names are expensive, and the bill arrives later.
Short names are a flex, not a strategy
OpenAI launched Dots on Tuesday, an always-on agent with a bubbly, blobby avatar. As a name, Dots is clean. It’s soft, it’s friendly, it fits the visual. It also collides with roughly everything. Dots is a puzzle game, a design system term, a pattern in a dozen UI libraries, and a plural noun that appears in every technical document ever written.
For a consumer product with a marketing budget, that’s survivable. Distribution wins. For those of us building on top of these systems, generic names cause real friction:
- Search becomes useless. Try troubleshooting an error message for a product whose name is a common English word. You’ll get puzzle games and CSS tutorials.
- Docs fragment. Community answers, forum threads, and blog posts stop being findable, which means the same problem gets solved a hundred times in private.
- Identifiers get ugly. When the obvious name is taken in your package registry or your internal namespace, you end up with prefixes, suffixes, and version numbers glued on. Those stick around for years.
- Logs lie to you. Grepping for a generic token in a multi-agent trace is a special kind of misery.
None of that stops a launch. All of it taxes the people building around it.
The domain was never the point
Here’s what I think actually happened, and I’m labeling it as opinion because the sources don’t settle intent: somebody at xAI saw a cheap, high-visibility opportunity and took it. Whether it was mischief or inventory, the effect is the same. A single DNS record generated more chatter than most product launches manage.
That tells you something about how thin the differentiation has gotten at the top of this market. Bloomberg Law reports that xAI has been competing with leading AI labs, including OpenAI, with mixed results. Mixed results is a polite way of saying the model quality gap isn’t the story it was two years ago. When capabilities converge, attention becomes the contested resource, and a domain name is a remarkably cheap way to buy some.
Which is also why it doesn’t matter much. Owning dots.com doesn’t make an agent more reliable. It doesn’t reduce latency, improve tool-calling accuracy, or fix the failure modes that make always-on agents hard to ship. The people evaluating whether to build on a platform aren’t checking the WHOIS record.
What I’d actually take from this
If you’re naming an agent this month, a few things I’ve learned the hard way:
- Pick the name and secure the identifiers in the same sitting. Domain, package name, org handle, repo. Not next quarter. The gap between “we decided” and “we registered” is where stories like this one live.
- Optimize for searchability over cuteness. A slightly odd name that returns clean search results is worth more to your users than a pretty one that returns noise.
- Separate the display name from the internal identifier. Call it whatever you want in the UI. Internally, use something specific and versioned. Your future self, reading a trace at 2am, will thank you.
- Treat naming collisions as a support cost. If your users can’t find answers, they file tickets instead.
The rivalry between these labs will keep producing moments like this, and they’re fun to watch. But the part worth copying isn’t the stunt. It’s the reminder that the small, unglamorous decisions you make before launch, the ones nobody applauds, are the ones that determine whether building on your thing feels good or feels like a chore.
Name your bots carefully. Buy the domain first. Then go make the agent work.
🕒 Published: