heartbeat

Send periodic heartbeats to keep crane-context sessions from timing out.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/venturecrane/crane-console --skill heartbeat-venturecrane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heartbeat
Source: https://github.com/venturecrane/crane-console/tree/main/.agents/skills/heartbeat
Command: npx skills add https://github.com/venturecrane/crane-console --skill heartbeat-venturecrane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a session from timing out by sending periodic heartbeats to maintain continuity.

Core Features & Use Cases

  • Detects the active session from the Context Worker and automatically updates heartbeat timestamps.
  • Displays last and next heartbeat scheduling to keep you informed during long tasks.
  • Useful during extended development sessions when /sod, /update, or /eod are not invoked frequently.

Quick Start

Run /heartbeat to refresh your active session and prevent timeouts.

Frequently Asked Questions about heartbeat

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

FAQPage Schema
How do I keep a development session from timing out during long-running tasks?

To keep a development session from timing out, you can trigger periodic heartbeats that automatically update session timestamps and maintain continuity during extended operations.

How do I send a heartbeat to refresh my active session?

You send a heartbeat by running the /heartbeat command, which locates your active session and updates the last and next heartbeat scheduling to prevent timeouts.

Do I need a valid CRANE_CONTEXT_KEY to maintain session continuity?

Yes, maintaining session continuity requires access to a valid CRANE_CONTEXT_KEY and the Crane Context API to locate the active session and update heartbeat timestamps.

When should I use automated heartbeats instead of manual session updates?

Automated heartbeats are useful during extended development sessions when manual update commands like /sod, /update, or /eod are not invoked frequently enough to prevent timeouts.

What is the best way to prevent CLI session timeouts in DevOps automation?

The best way to prevent CLI session timeouts in DevOps automation is to use an automatic heartbeat mechanism that detects the active session and periodically refreshes its timestamps.