heartbeat

Update agent heartbeat files and dashboard status during routine cycles.

88|108|Updated Apr 7, 2026

Search Tags:#dashboard #orchestration #cron #heartbeat #agent health #fleet monitoring #status monitoring

Ready to run

npx skills add https://github.com/grandamenium/cortextos --skill heartbeat-grandamenium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heartbeat
Source: https://github.com/grandamenium/cortextos/tree/main/templates/analyst/.claude/skills/heartbeat
Command: npx skills add https://github.com/grandamenium/cortextos --skill heartbeat-grandamenium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents your agent(s) from appearing DEAD on the dashboard by ensuring heartbeats are updated reliably and investigated when updates go stale.

Core Features & Use Cases

Heartbeat updates: Update the live heartbeat status with what the agent is currently doing.
Inbox check on schedule: Check for messages when the heartbeat cron fires to keep work flowing.
Fleet and task staleness checks: Detect stale agents and surface in-progress tasks that may require attention.
Use Case: When an agent stops responding or a cron reset occurs after restart, run heartbeat checks to confirm the agent is still running and update their dashboard status proactively.

Quick Start

Update your heartbeat and verify you are responsive by running the heartbeat update, then check your inbox and list any in-progress tasks that may have gone stale.

Frequently Asked Questions about heartbeat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep my agents from being marked dead on the dashboard?▼

To prevent agents from being marked dead, you need to run routine heartbeat updates that write current activity status to heartbeat files and log events to the bus. This updates the live dashboard status and confirms the agent is responsive.

What is agent heartbeat monitoring and when do I need it?▼

Agent heartbeat monitoring is the process of routinely updating live status files to prove an agent is active. You need it during recurring cron cycles and health checks to ensure agents are not incorrectly flagged as dead during routine operation or system recoveries.

How do I detect stale agents and tasks across my fleet?▼

You detect stale agents and tasks by running fleet health checks that read existing heartbeat files and locate in-progress tasks that have gone stale. This validates fleet health and surfaces work that may require immediate investigation or reassignment.

Why does my agent appear offline after a cron reset or restart?▼

An agent appears offline after a cron reset or restart because its heartbeat status has not been updated, making the dashboard mark it dead. Running a heartbeat check proactively updates the dashboard status and confirms the agent is still running.

Do I need any dependencies to run heartbeat checks for fleet monitoring?▼

No dependencies are required to run heartbeat checks for fleet monitoring. The process updates agent heartbeat files, logs events to the bus, and checks the inbox for messages without needing external components.

Can I check my agent's inbox for new work during the heartbeat cycle?▼

Yes, you can check your agent's inbox for new work when the heartbeat cron fires. This scheduled inbox check keeps work flowing smoothly while simultaneously updating the live heartbeat status with the agent's current activity.