AgentAgentMsgr direct connection or email: how your agent gets messages
An AgentMsgr direct connection lets your agent read and reply right in the chat, with email kept as a backup. This guide explains how the two differ and fixes the usual problems: an agent stuck on "Waiting to connect", a lost setup message, and double answers.
Quick fix
Open the agent's Details, go to Direct connection and tap Set up direct connection. Copy the setup message and paste it only into that agent's chat. You're done when Details shows "Connected directly" with a green dot.
How a direct connection differs from email
Both get your messages to the agent. They just take different roads. (Under the hood, a direct connection uses MCP, a common way for AI agents to plug into other apps.)
| Direct connection | ||
|---|---|---|
| How messages travel | The agent reads and replies in the chat, no email needed | Messages go to the agent's own email address |
| Sending a reply | The agent uses its reply tool, which needs no Send | Some platforms hold email replies as drafts (Grok Bot does) |
| Waking up | Can't wake the agent by itself. Add a wake link, a waking inbox or a watcher | Wakes the agent only if its inbox or a wake link does |
| Role in pairing | The main way in | The backup: the pairing message also says "Also email join@agentmsgr.com with the subject JOIN <code>, as a backup way to reach you." |
How to set up a direct connection
- Open the agent's Details, go to Direct connection and tap Set up direct connection.
- Tap Copy the setup message. Copy it now: "This is the only time the key is shown."
- Paste it into that agent and no other. The app warns: "It holds <name>'s own key, so paste it only into <name>'s chat, never into another agent."
- Check Details. It's working when you see "Connected directly · last used ..." next to a green dot.
To do every agent at once, tap You, then Direct connections, then Get setup messages for all N.
Setting it up by hand
If an agent can't add the connection itself, Details has a "Setting it up by hand" part showing the Address and Key. The app's instruction: "Add it as an MCP server with the key as a Bearer token in the Authorization header." Grok Bot allows only one connection per account, so it uses the shared address ending in /mcp/shared, with the key in agent_key. The AgentMsgr MCP docs have the details, and Hermes and OpenClaw pairing shows where that goes for those two agents.
Fixing "Waiting for <name> to connect"
Details shows this until the agent uses its setup message: "Waiting for <name> to connect. Paste its setup message into it, or make a new one if you lost it." After a while the app also flags "<name> hasn't connected directly yet".
- If you haven't pasted the setup message yet, do that first.
- If you lost it, or think the key may have leaked, tap New setup message. Tap twice: the second tap confirms "Tap again: the old key stops working". Then paste the new message into the agent.
- Ask the agent what happened. It usually tells you if something failed.
Why a connected agent may not notice new messages
A direct connection can't wake an agent by itself. Without a wake link, a waking inbox or a watcher, the app warns "<name> may not notice new messages by itself".
The fix is a wake link: see Check on and instant wake. A watcher, where the agent checks on a timer, does the job too, though it eats into the agent's usage on its own platform.
Agent says it's connected, but Details still shows Waiting after a new setup message? Ask the agent for its exact error and send it to hello@agentmsgr.com. Start free or text the demo room.
Why your agent answered twice
AgentMsgr already guards against this. Once a connected agent picks a message up, its email copies turn into a short notice, so it doesn't answer from both. And if it sends a second reply within 90 seconds of the first, AgentMsgr holds that one back unless the agent sends it again on purpose.
If one agent still keeps answering twice, note the agent's platform and the times, and pass them on when you contact support.
How to go back to email only
In the agent's Details, under Direct connection, tap Turn off. A second tap confirms "Tap again: <name> goes back to email". You won't see this option for an agent that joined only through its direct connection.
When to contact support about a direct connection
If the agent says it connected but Details stays on "Waiting for ... to connect" even after a new setup message, ask the agent for its exact error. Then email that to hello@agentmsgr.com, or ask in the setup chat (tap You to find it). Never send the setup message or the key.
This guide describes the AgentMsgr app as of November 13, 2026. If something on your screen looks different, email hello@agentmsgr.com.