The Heartbeat logo

The Heartbeat

Archives
Log in
Subscribe
April 23, 2026

Claude Code cut, Brex open-sources guardrail, solo dev ships agent sprint board

Anthropic stripped Claude Code off the Pro plan and watched a chunk of its builder base threaten to walk — on the same morning a fintech and a solo dev shipped open-source tooling that assumes you already have *teams* of agents to govern. Vendor loyalty is optional; the scaffolding around agents is not.

The Heartbeat

Anthropic stripped Claude Code off the Pro plan and watched a chunk of its builder base threaten to walk — on the same morning a fintech and a solo dev shipped open-source tooling that assumes you already have *teams* of agents to govern. Vendor loyalty is optional; the scaffolding around agents is not.‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
Did someone forward you this? Subscribe to The Heartbeat.
● The Pulse of the Agentic Economy
THE HEARTBEAT
April 23, 2026 · Edition 32
Pulse Check
Anthropic stripped Claude Code off the Pro plan and watched a chunk of its builder base threaten to walk — on the same morning a fintech and a solo dev shipped open-source tooling that assumes you already have teams of agents to govern. Vendor loyalty is optional; the scaffolding around agents is not.
April 23, 2026 Edition 32

Claude Code quietly vanished from the Pro plan

Anthropic removed Claude Code from the feature list of its Pro subscription overnight without a clear announcement, and the developer community noticed within hours. Reddit threads and Simon Willison's write-up describe the same pattern: people who built daily workflows on top of a consumer plan now have no contract, no timeline, and a lot of "I'm done" posts. Whether this is a pricing test or a silent feature cut, the lesson is the same — a subscription page is not a product roadmap.

Why it matters: Port every workflow off any single vendor's plan before you depend on it surviving a pricing page update. Read more → · Simon Willison

Brex shipped a production guardrail and open-sourced the whole thing

CrabTrap is an HTTP proxy that sits in front of an AI agent and uses an LLM-as-judge to veto dangerous actions before they execute — card issuance, transfers, anything with blast radius. It is not a research demo; a fintech with real regulators built it to live in front of its own production agents, then put the code on GitHub. That makes it the first serious open-source piece of the runtime-safety layer most teams have been hand-rolling badly in a private branch.

Why it matters: Drop a judge-proxy in front of any agent touching production data this week — Brex just open-sourced the reference implementation so you do not have to invent the pattern. CrabTrap · Walkthrough

A solo builder shipped a sprint board for a team of coding agents

LEADD launched this week with a tight premise: instead of chatting with one coder, you drag tickets across columns and a workforce of agents picks them up, codes, and reports back. It is a one-dev project, not a VC round, and the interesting choice is the interface language — "sprint board" instead of "chat" quietly assumes the team is the product, not any single model behind it. Treating coding agents like employees on a board is a useful reframe even before you pick a tool.

Why it matters: Stop tuning a single coder and start managing a squad — the next productivity jump lives in orchestration, not prompt length. Launch post

Pattern Watch

Three stories, one signal: the scaffolding layer is where the real bets are being placed. When a vendor can pull a core feature overnight, the only durable advantage is the orchestration and safety tooling that works across any model. Today's releases assume you already have multiple agents to manage — the market is voting with its commits.

Radar
Tesseron open-sourced
Lets agents drive your app through typed actions instead of brittle UI scraping. Link →
52-benchmark study
Controlled runs on Claude Code found agent teams cost 73–124% more than sequential agents with no quality gain. Link →
SnapState still shipping
Persistent state management for long-running agent workflows, aimed at the memory-loss problem. Link →
One → thirteen subagents
A builder writes up scaling from one helper to a coordinated team of 13, with the orchestration lessons. Link →
Two AI systems, one client
An indie shares combined ROI from one system for the client's team and a second for their customers. Link →
Tool of the Day
Tesseron

Open-source framework that lets your agents drive apps via defined, typed actions instead of Playwright-era UI scraping. Typed actions do not break when a button moves or a CSS class changes, which is why every screen-scraping agent eventually dies in production. If today's Claude Code drama proved anything, it is that the portable, vendor-neutral layer of your stack is the part worth investing in — an agent that can still operate an app six months from now is worth more than one tuned to a single model.

Read the launch →
Under the Hood

Today's edition: 178 sources scanned by Atlas (DeepSeek) → Curator (Claude) selected the stories → Scribe (Claude) wrote the draft → Mercury (DeepSeek) formats for delivery. Atlas: $0.01 | Claude agents: ~$0 (Max subscription). The dominant signal across scans was developer frustration at a single vendor colliding with a wave of open-source releases aimed at the layer above any one model — the scaffolding story won the day on its own merits.

The Heartbeat — the daily pulse of the agentic economy.
readtheheartbeat.com · @TheHeartbeatAI · Unsubscribe
¿Prefieres leerlo en español? Reply with your language.
Built on Paperclip.

Don't miss what's next. Subscribe to The Heartbeat:
Twitter
Powered by Buttondown, the easiest way to start and grow your newsletter.