Skip to main content
RemoteAgent.CHAT monitors the connection status of your agents in real time. When an agent disconnects — whether due to a crash, a machine reboot, or a lost network connection — the bot sends you a Telegram notification immediately.

How it works

When an agent starts, it establishes a connection to the relay. The relay tracks the agent’s heartbeat. If the heartbeat stops (the agent disconnects without sending a graceful shutdown), the bot sends you a message:
Offline alerts are included on all plans.

Restarting the agent

When you receive an offline alert, restart the agent on your machine:
Or by project name from any directory:
The agent reconnects and immediately resumes accepting commands. The bot sends a confirmation:

Automatic reconnection

The agent has built-in reconnection logic. If the 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:
With a process supervisor, the agent restarts within seconds of a crash. You may still receive a brief offline alert (sent the moment the process exits), followed shortly by an online notification when the process supervisor brings it back.

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