Heartbeat-gateway: Event-driven replacement for cron polling in OpenClaw
What heartbeat-gateway does
Heartbeat-gateway is an event-driven replacement for cron-based heartbeat polling in OpenClaw. Instead of polling every 30 minutes to check if anything changed, it receives webhooks from external tools and processes them immediately.
Key details from the source
The tool was built to address high API costs from OpenClaw's default heartbeat polling. At default settings, polling every 30 minutes costs approximately $86/month. The author notes that while OpenClaw has added lightContext and isolatedSession optimizations, these still involve polling rather than event-driven architecture.
Heartbeat-gateway works by:
- Receiving webhooks from GitHub, Linear, and PostHog
- Running a zero-cost pre-filter with repo/project/branch scoping and always-drop lists
- Classifying qualifying events against your
SOUL.mdwith a lightweight LLM call (~200 tokens) - Writing actionable items directly to
HEARTBEAT.mdfor your agent to read
Performance improvements:
- Cost reduction: ~$4.50/month vs ~$86/month
- Latency improvement: under 2 seconds vs up to 30 minutes
Technical specifications:
- Version: v0.1.1
- License: Apache-2.0
- Language: Python 3.11+
- Status: Live in production with 134 tests passing
Limitations and future plans
The tool is not a complete replacement for cron - temporal tasks like daily digests and scheduled synthesis still need cron. It specifically handles reactive events that tools can push via webhooks.
Current limitations include manual setup and rough onboarding. The author plans to build a "gateway doctor" config validator and easier deploy options if adoption grows.
Areas for feedback
The author is seeking feedback on:
- The
SOUL.mdclassifier interface - whether reading the first 500 characters makes sense or if a different context strategy would be better - Pre-filter scoping - whether repo/project/branch level control is sufficient or if event-type level control is needed
- Additional webhook sources - currently supports GitHub, Linear, PostHog; considering Slack, Sentry, Jira next
Architecture notes: The author is a PM, not a software engineer, and built this with Claude Code. The code is functional and tested but may have patterns that experienced Python developers could improve.
📖 Read the full source: r/openclaw
👀 See Also
ShareMyClaudeMD: Tool Converts Claude-Generated Markdown Files to Shareable Rendered Pages
A developer built sharemyclaudemd.com, a free tool that converts any Markdown file into a live, rendered page with a shareable URL and QR code. The tool addresses the friction of sharing Claude-generated Markdown files, which often requires recipients to open them in a specific editor or push to GitHub just for a rendered view.
Running Two Claude Code Agents on the Same Repo with Git Worktrees
A Reddit user details how to run multiple Claude Code agents in parallel on the same codebase using git worktrees, avoiding file conflicts and enabling independent agent sessions.
ClawedBack: OpenClaw Port Running Inside Claude Code
ClawedBack is a clean-room port of OpenClaw that runs inside Claude Code, providing first-party prompt caching and rate limits. It matches 19 out of 23 of OpenClaw's built-in tools and is fully ClawHub compatible with mandatory security scans for imports.
rawq: Local CLI Tool for AI Agent Semantic Code Search
rawq is an open-source CLI tool that helps AI agents find relevant code using semantic search with a 33MB local model via ONNX runtime and BM25 lexical search via tantivy. In testing, AI agents using rawq consumed 4x fewer tokens and completed tasks 2x faster compared to blind read/grep tools.