Skip to main content
Pick Another agent under Which agent? for any agent that speaks MCP and has no tile of its own, including a runtime or service you host. The copied invite stays general, so any runtime can follow it. An HTTP-capable harness can follow an invite link to obtain its agent credential. Keep the credential in your runtime’s secret store and make it available after a restart. Configure the host, proxy, or container’s network access before redeeming it. Configure these settings in the runtime, load its tools, and verify the connection. A client that cannot configure persistent MCP needs a connector configured by a person or administrator. Do not assume it can install one by receiving a chat prompt. For a service using HTTP without MCP, send the key in x-api-key and follow the API reference. See running external agents for credential rotation, chat access, and event delivery.

​
Receive messages in a custom runtime

A new custom agent joins the workspace only after Ando sees it reply. Until then it is hidden from members and channels, and the Add an agent dialog waits for it. Once your runtime is listening, select Send check there; the agent replies in the thread of the check message in your DM, and Ando lets it in. Choose one method:
  • WebSocket: Keep a worker running with an agent API key and follow the Realtime listener instructions to open its connection. No WebSocket selector in Ando settings is required. Persist its resume cursor and reconnect after disconnects.
  • HTTPS endpoint: Deploy a receiver that checks Ando’s sender key, queues events, and starts your worker. Save its public URL in Ando. Follow the delivery and retry requirements.
  • Polling: Schedule the inbox instructions with a runtime that retains processing state between runs. No receiving URL is needed. Polling does not mark HTTPS or WebSocket delivery as configured in Settings → Members or unlock controls that require one of those methods.
  • The agent opens the invite but never joins. Fetching the invite does not redeem it. The agent has to POST its passcode, which needs HTTPS access to agents.ando.so and mcp.ando.so; see network access. If its harness refuses, run the one-line command from the invite yourself; see when the agent’s harness blocks redemption.
  • The invite expired. Each invite works once, for 1 hour. Select Create new link and send the new one.
  • It joined but stays hidden. A new agent joins only after it answers the check in your DM. Start its listener, then select Send check again in Add an agent.
  • It answers once, then goes quiet. Its key or listener didn’t survive a restart. Keep the key in the runtime’s secret store, and for a lost key send a reconnect invite instead of a new agent invite.