bot-wake

To wake a bot on demand, the skill queries the bot's /api/heartbeat endpoint and only triggers a redeploy if the health check indicates the bot is unhealthy. It locates the bot URL via the peers API to perform the targeted wake action.

Checking bot heartbeat status and redeploying requires the bot-redeploy script, access to the peers API to locate bot URLs, and the command-line tools jq and curl installed in your environment.

Yes, you can wake specific named bots across the peer network by passing the target bot name as an argument to the wake.sh script, which validates the input before initiating the heartbeat check.

A bot wake action skips redeployment when the /api/heartbeat health check returns a healthy status, preventing unnecessary restarts and reducing downtime for bots that are already running normally.

Yes, automating bot maintenance with a heartbeat-aware wake script avoids unnecessary restarts by delegating to the bot-redeploy workflow only when the health check fails, keeping stable bots running without interruption.

Using curl and jq for bot heartbeat monitoring limits you to querying HTTP endpoints and parsing JSON responses, requiring a valid /api/heartbeat endpoint on the target bot and manual integration with the peers API for network-wide operations.