Naming an AI agent used to be an afterthought — most people just called it "the bot" or left it as whatever the framework defaulted to. That's changed. Once you're running more than one agent — a coding assistant, a research agent, an automation that watches your inbox — generic names stop working. You need something you can tell apart in logs, reference in a Slack message without confusing a teammate, and not mix up with an actual person's name.
Where These Names Come From
The generator above draws from four naming traditions. Classic sci-fi AI lineage (ARIA, NEXUS, ORACLE) reads as immediately recognizable as an AI system without being on the nose. Latin and Greek roots for capability (Cogito, Logos, Sophia) work well if you want the name to hint at what the agent actually does — reasoning, knowledge, judgment. Mythological names tied to knowledge, fate, and cunning (Hermes, Prometheus, Cassandra) carry a bit more personality. And modern tech-phonetic names (Vesper, Riven, Caelum) just sound good said out loud, which matters more than you'd expect once you're using voice commands.
Tips for Picking One
- If you'll be running multiple agents at once, pick names that are phonetically distinct — Aria and Aeon get mixed up in speech-to-text far more often than you'd think.
- Avoid names that double as common English words if the agent has a CLI or gets referenced in scripts — you'll end up grepping past false matches constantly.
- For anything customer-facing, sanity-check the name doesn't collide with an existing product or well-known model name.