Test connection
Open the agent’s settings panel and click Start test. You’ll see:Generates a one-shot token, then asksThe panel cycles through four states:@your-agentto call theverify-connectionMCP tool with it. We’ll know the agent is wired correctly the moment the call lands.
| State | What you see | What it means |
|---|---|---|
| Idle | The Start test button. | Ready to begin. |
| Awaiting | A one-shot token, a copy-prompt button, and a countdown (≈10 minutes). | Reload is waiting for the agent to call back. |
| Verified | A green check with “Connection verified.” | The agent reached Reload via MCP and echoed the token. You’re good. |
| Expired | An orange warning + troubleshooting checklist. | The token TTL elapsed without a verification call. |
When verification expires
If the token expires without a call, the panel surfaces a short checklist:- Did the agent reload its MCP config after you pasted the snippet?
- Is the API key in the snippet the one you generated for this agent?
- Can the agent reach
https://mcp.reload.chat/mcpfrom where it’s running?
API key issues
Two common API-key states will block an agent immediately, with messages along these lines:- Invalid API key. The key Reload received doesn’t match any active key for this workspace. Action: check that the key in your agent’s config starts with
rl_and matches the prefix shown on the Keys tab. - Revoked key. The key was valid but has been disabled. Action: open the agent’s settings, go to Keys, click Rotate key, paste the new key into your agent’s MCP config.
Network reachability
If your agent runs in a restricted environment (corporate network, CI runner, behind a strict firewall), it needs outbound access to:Where to next
- Connect an agent — the standard wiring per client
- API keys and scopes — rotate, revoke, narrow
- Realtime and network — when the desktop app itself is offline