How it works
When an agent starts, it establishes a subscription to its Redis command channel. The web app tracks the agent’s heartbeat. If the heartbeat stops (the agent disconnects without sending a graceful shutdown), the agent’s status is set tooffline in the database and the bot sends you a message:
Plan availability
| Plan | Offline alerts |
|---|---|
| Trial | Included (Pro features for 14 days) |
| Solo | Included |
| Pro | Included |
| Team | Included |
Restarting the agent
When you receive an offline alert, restart the agent on your machine:Automatic reconnection
The agent has built-in reconnection logic. If the Redis connection drops temporarily (e.g., a brief network blip), the agent attempts to reconnect automatically with exponential backoff. You will only receive an offline alert if the connection cannot be restored within the reconnection window. This means transient network issues are handled silently — you only get notified for meaningful outages.Setting up automatic restarts
To minimize downtime without manual intervention, run the agent as a supervised process that restarts automatically:Checking agent status manually
You can check the status of all your agents at any time by sending/agents to the bot, or by visiting the dashboard.
The dashboard shows:
- Current status (online / offline)
- Last seen timestamp
- Number of active sessions