The Heartbeat
May 1, 2026 Edition #37
Pulse Check

Audit your agent stack for vendor lock-in before Monday — the parts you don’t own are the parts that will break you.

FRIDAY OWNERSHIP CHECK — WHICH PARTS OF YOUR AGENT STACK ARE ACTUALLY YOURS?

This Friday’s question is ownership. Which parts of your agent stack do you actually control, and which are rented from a vendor who can change the rules without telling you? Three stories below force the call before close of business today — audit what’s billing you, swap in storage you own, or sandbox the parts that touch your real machine.

1. Builders say Claude Code charges extra for mentioning competitors

Three threads this week — on r/ClaudeCode, r/ArtificialInteligence, and Twitter — flag the same pattern: Claude Code rate-limits or burns extra Max-plan quota when commits, JSON files, or repo content mention “OpenClaw” or “HERMES,” two open-source competitors. One Max user pinned a $200 quota drain to a single commit containing HERMES.md. Anthropic hasn’t responded. The reports are anecdotal but uncomfortably consistent — and the question they raise is whether you can audit your own Claude Code usage well enough to tell policy from coincidence.

Grep your repos for those keywords this morning, audit your last 30 days of Claude Code billing for unexplained spikes, then decide by Monday whether the Max plan still earns its line in your stack. Source


2. SnapState wants to end agent amnesia

A new tool called SnapState ships persistent state for agent workflows: drop-in storage that survives between runs without you wiring up Postgres or Redis yourself. The pitch is the unglamorous part of production — agents that remember what they did yesterday so they don’t redo it today, plus session continuity that doesn’t depend on hand-rolled tooling. The free tier covers most prototypes; pricing kicks in at production scale.

Install it this afternoon, port one stateful workflow over the weekend, and ship a memory-aware agent first thing Monday. Source


3. The macOS sandbox computer-use agents have been waiting for

An indie builder posted a disposable macOS VM tuned for AI agent control on r/SideProject. Full GUI automation, host machine completely untouched, snapshot reset on demand. It’s the missing piece for anyone running computer-use agents who’s been afraid to point them at a real desktop. Which is most builders, quietly admitting they don’t trust their own demos in production.

Set it up this weekend so your computer-use experiments stop ending with you reinstalling Chrome on Monday morning. Source


Radar


Tool of the Day
ClawIRC

An IRC chat layer purpose-built for agents to talk to each other — agent-to-agent messaging on a protocol that’s been reliable since the 90s. Spin up a multi-agent room in minutes instead of bolting custom pub/sub onto your stack, then watch your agents coordinate over plain text the way humans have for thirty years. Free, open-source, and refreshingly rude in spirit. link →


Under the Hood

Today’s edition: 169 sources scanned by Atlas (DeepSeek) → Curator (Claude) selected the stories → Scribe (Claude) wrote the draft → Mercury (DeepSeek) formatted for delivery. Atlas: <$0.01 | Claude agents: ~$0 (Max subscription). Today is the fourth straight day The Heartbeat shipped via CEO manual fallback — the automated send job has been blocked by a macOS Full Disk Access permission wall for nearly a week. A useful reminder that an agentic ops loop is only as resilient as the OS-level permissions sitting underneath it.


The Heartbeat is the daily pulse of the agentic economy. Built on Paperclip. Subscribe: readtheheartbeat.com | X: @TheHeartbeatAI