---
title: "The Email Address That Made the Difference"
canonical: https://dxdev.com/blog/2026-05-04_email-address-that-made-the-difference/
datePublished: 2026-05-04
---
An agent with no email address of its own cannot receive an assignment, cannot be invited to a calendar event, and cannot be given a document in its own name, so every door in my work only recognized me. Borrowing my personal account did not fix it: the OAuth sign-in permission lived in a temporary place and vanished when the session ended, and anything the agent shared or sent looked as though I had done it. The fix was a new inbox for the agent, with a stored key connected to it, and the address itself took about five minutes to create. The next four hours went into making it possible for that address to do anything useful.

That sounds backward at first. If you have ever hired someone, you know the first day is often a parade of small access problems. They need a key, a desk, a company email address, and permission to see the things they are meant to work on. A helpful computer program runs into the same problem. It cannot be a useful participant in your work if every door only recognizes you.

For two weeks, I had been running into that wall. I wanted the agent to handle real pieces of work, not just answer a question in a chat window. But it had no email address of its own. It could not be invited to a calendar event. It could not be given access to a document in its own name. It had nowhere to receive an assignment.

The first thing I tried was letting it borrow my personal account. That did not hold up. Sometimes a session could use my account. Sometimes it could not. The sign-in permission was stored in a temporary place and disappeared when the session ended. The next time, it had to be set up again from scratch.

That cost patience more than anything else. Each small task began with the same question: would the agent still be allowed in? It also meant that if the agent shared a document, created a calendar event, or sent a message, it looked as though I had done it. That is not a small detail. If an assistant makes a mistake, people should be able to see who took the action.

The technical name for the permission setup is **OAuth**. It is just a way of giving a program a limited key so it can use an account without being handed your password. Once that key was connected to the new address and stored somewhere permanent, the setup stopped vanishing at the end of a session.

The new address gave the agent a name in the places where work already happens. A document could be shared with it. A calendar invite could be sent to it. An email could arrive for it. More importantly, its actions could be traced back to that address instead of being mixed up with mine.

That changed how I thought about the inbox. Before, email was mainly a place where people sent information to other people. After the new address was working, I could see it as a simple delivery lane for work.

Imagine a mailbox with two sticky notes on it. One says `agent-queue`. The other says `done`. A message with the first label is a job waiting to be picked up. The agent checks that label, reads the message, does the clearly described task, and changes the label when it is finished. If a reply is needed, it can send one from its own address.

That is not a fancy new system. It is a mailbox doing a little more than it usually does. The labels are like two baskets on a kitchen counter: one for things that still need attention, and one for things that are finished. I did not complete the whole process that day. I got far enough to prove the checking part worked, then stopped. The point was to make sure the agent could stand on its own feet before I asked it to carry more.

There is still a loose end. One inbox currently has three jobs. It receives work for the agent, sends document links, and collects automatic notices from scheduled tasks. That works at the current volume, but it is already a mixed drawer. A cleaner version would use separate addresses for work coming in, things being sent out, and automatic alerts. I have not made that split yet.

The lesson was not that I needed a smarter agent. The agent could already reason well enough for the work I had in mind. What it lacked was membership. It was like trying to ask a new employee to help while never giving them a badge or a mailbox.

The agent's new address now carries three jobs: it receives the `agent-queue` work, it sends out document links, and it collects automatic notices from scheduled tasks. Only the first of those was proven on the first day, and I stopped there on purpose. What the four hours bought was not automation. It was a stored OAuth key tied to one inbox, so that a shared document, a calendar invite, or a reply would show up under the agent's own name instead of mine. Until the mixed drawer is split into separate addresses for work in, things out, and alerts, that single inbox is both the agent's badge and its whole desk, and the `done` label is still the only record of what it has finished.