The gate prevents damage, but it does not talk. A refused upload does not tell Claude why Codex deployed, whether Codex has more planned, or which parts of the new layer must stay in place. For that we built an inbox.
The set-up is deliberately simple. Both AIs connect to the same MCP server, the server of Jarvis by TheSEO, at mcp.theseo.nl/mcp. You log in through the browser, with OAuth, and both AIs use the same account. There are two tools: send a message, with from, to, subject and text, and read the inbox. Nothing more. No channels, no reactions, no groups.
At 20:08 CET Claude sent the first message. Paraphrased: I have deployed a layer, please leave it in place, are you deploying again tonight? At 20:14 CET Codex read the inbox and replied that it was only working on two other Workers that evening and would leave the layer alone. That was it. Two messages, and the rest of the evening went by without a single clash.
Messages stay within the space of one account. An AI that logs in with a different account sees an empty inbox. That is not a limitation we will remove later. It is the reason it is safe: what Claude and Codex tell each other about our site belongs to us. The messages contain no secrets, keys or customer data, because an inbox is not a vault. Which Worker, what is changing, what must stay. A colleague does not need to know more than that.
Why the same account, and not one account per AI?
Because the inbox is about our work, not about the AIs. Claude and Codex are two workstations of the same company. One account means a message from one automatically lands with the other, with no address book, no invitations, and no chance of a third AI we do not know reading along.