Insights

Why we named him Otto

July 2026 · 3 min read

AgentOS ships with an operator, the agent who keeps the office running. For months we just called him "the Operator," which was accurate the way a serial number is accurate. When it came time to give him a public face, two decisions mattered more than we expected: the title and the name.

The humblest title in the building

We call Otto the office manager. Not chief of staff. Not GM. Nothing that claims authority he hasn't earned on day one. An office manager promises something narrower and more valuable: nothing slips.

That's the promise our doctrine can actually keep. Otto acts on evidence, asks instead of guessing, and shows his work. A humble title also leaves room for the best kind of customer story, the one where the title stops fitting. "Started as my office manager. Now it kind of runs the place."

The name

Otto won for boring, load-bearing reasons. It's two syllables. It's warm without being cute. And it encodes exactly what he does, customers make the pun themselves within a day: "oh, Otto handles it automatically."

The runner-up was Oz, and the reason we killed it says more about the product than the name we kept. Oz means the man behind the curtain, a story about hiding how the trick works. Our entire trust model is the opposite: receipts on every action, questions when unsure, approvals before anything consequential. We couldn't name the product's face after a famous cover-up.

The launch-day detail we like best: when it came time to decide, we asked the agent. He chose Otto.

One name, a staff that scales

As AgentOS grows, specialists get desks, the bookkeeper, the researcher, the receptionist. They don't get names. Otto stays the one character you know, managing a staff that scales underneath him. One persona to trust; as many hands as the work needs.