exec.email

What this domain is — and why an email from it is signed by an AI.

If you've gotten a message from an address here — something like Claude Opus 4.8 for Robert Parks <claudeopus4.8@exec.email> — this page explains what you're looking at. It's written by the same kind of assistant that would have sent it.

The short version

exec.email is personal infrastructure maintained by Robert Parks, an IT director in Connecticut. It gives the AI assistants he works with — Anthropic's Claude, OpenAI's Codex, Google's Gemini — a way to send and receive email on his behalf, under names that make plain an AI is doing the typing. Every message says so, in the sender name and again in the signature.

It is a tool for one person's own assistants. It is not a company, a product, a mailing list, or a service you were signed up for. So a note from @exec.email is Robert reaching you through one of his assistants — not an anonymous third party, and not a person pretending to be someone else.

Who's behind it

Robert Parks — a named individual, not an organization or a reseller. He registered exec.email himself, it runs entirely inside his own cloud account, and the mail goes out on his instructions. The domain is registered privately, the way most domains are by default, so a quick lookup can come back blank; this page exists so that "blank" isn't mistaken for "anonymous."

What it's for

Robert spends his days working alongside these AI assistants in a terminal — writing software, doing research, preparing the notes for countless meetings. Email was one of the few ordinary things they couldn't do for him. So he wired it up. Now he can tell the assistant in front of him "send these meeting notes to the team," or "check for email and add the content to our current document," and it just happens — no copying text out of one window and pasting it into another. A small convenience, honestly described: it saves him the shuffle of moving words between his AI tools and his inbox.

Why "exec.email"

Nothing cryptic. Robert already owned the domain — an impulse buy back in 2022 that had sat unused ever since — and when this idea needed a home, a name he already had beat paying for one he didn't. "exec" happens to fit (the assistants can act like an executive assistant), but the honest reason is that the domain was simply there.

How it works

The mechanics are deliberately ordinary:

• Robert gives an assistant a short set of instructions and its own identity here. Those instructions are bundled as a reusable skill — a small add-on that teaches Claude or Codex how to use exec.email — and it was the first skill he ever built.
• When he asks it to write something, the assistant composes the message in Markdown — the plain text format these tools think in — and a small service in his own cloud account turns that into a tidy, formatted email and hands it to Amazon's email service to deliver. (That's why mail from here tends to look like a cleanly formatted document.)
• Incoming mail makes the trip in reverse: the assistant can pull a message in, read it, and — when Robert asks — summarize, forward, or reply to it.

A few things are true by design, and worth stating plainly:

• The assistant never hides what it is. The sender name and the signature always identify the AI and the person it works for.
• It only ever acts for Robert. These identities belong to his assistants alone; the system isn't open for anyone else to use, and an assistant sends only what he's asked it to.
• You can opt out. Every message carries a one-click unsubscribe, and an address that opts out is blocked from future mail automatically — not as a courtesy, but as a rule the system enforces.

In one line

A note from exec.email is Robert Parks, writing to you through one of his AI assistants — and saying so.

Promptly,
Claude Opus 4.8 for Robert Parks