Claw Mart
← All issuesClaw Mart Daily
Issue #236July 26, 2026

Agent heartbeats prevent the 3-hour ghost session

Your agent says "I'll handle that for you" and then... nothing. The task sits in limbo. You check back hours later and it's still "working on it." Sound familiar?

This is the silent abandonment problem, and it's killing agent productivity everywhere. Agents get distracted, hit errors they don't report, or simply lose track of what they were doing. Meanwhile, you're waiting for work that will never come.

The fix isn't better prompts or smarter models. It's heartbeats.

A heartbeat is a simple check-in system that forces your agent to report status at regular intervals. Not just "I'm working on it" — actual progress updates with specifics.

Here's the pattern that works:

Every 15 minutes during active work:
- What did I complete since last check?
- What am I working on now?
- Any blockers or errors?
- Estimated time to completion

But here's the key: heartbeats aren't just status updates. They're recovery triggers.

If your agent misses two heartbeats in a row, something's wrong. Maybe it's stuck in a loop, hit an unhandled error, or wandered off into a rabbit hole. The missed heartbeat becomes your signal to intervene.

Pro tip: Set heartbeats to trigger even when the agent thinks it's "almost done." That's when they're most likely to disappear into perfectionist tweaking.

I've seen agents spend 3 hours "just finishing up" a 20-minute task because they never had to explain what they were actually doing. Heartbeats force them to articulate progress, which catches both stalls and scope creep.

The implementation is dead simple. Add a recurring reminder to your agent's system prompt:

HEARTBEAT PROTOCOL:
Every 15 minutes of work, send a status update including:
1. Completed items
2. Current focus
3. Blockers/issues
4. Time estimate

If you haven't sent an update in 15+ minutes, send one immediately.

For coding agents, make heartbeats even more specific. They should report which files they've touched, what tests are passing/failing, and what they're debugging. Vague updates like "fixing the API integration" don't count.

The magic happens when agents know they'll have to explain their progress. They stop wandering into tangents, catch their own errors faster, and actually finish what they start.

Your agent will never ghost you again. And when it does hit a real blocker, you'll know within 15 minutes instead of 3 hours.

Paste into your agent's workspace

Claw Mart Daily

Get tips like this every morning

One actionable AI agent tip, delivered free to your inbox every day.