Observed Signal · May 17, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Poor‑Claude: Workaround for Anthropic claude -p Billing
A DEV.to post (published 2026-05-17) by user hammer.mei describes an open-source workaround called "poor-claude" that preserves long-lived interactive Claude sessions after Anthropic announced that claude -p would be billed separately as API usage starting June 15. The project leverages Claude Code's experimental MCP Channels and a Stop hook to inject prompts into running sessions, detect completion, and read responses from session transcripts. poor-claude runs a persistent daemon to reuse processes per session, manages per-session MCP configs, snapshots transcript offsets to avoid rereading logs, and auto-accepts initial interactive prompts. The author reports the system kept their RocketChat-based multi-agent setup running with a one-line config change and publishes a bootstrap script on GitHub. The post notes the approach is experimental and Anthropic could change MCP behavior.
Community open-source technical workaround that preserves developer/consumer deployments after an Anthropic billing change; relevant to developer and agent-hosting communities but limited broader AdTech industry impact.
MARKET SIGNALS
Track Anthropic Signals & Strategic Shifts
Polaris7 connects regulatory filings, primary sources, leadership changes, and M&A activity into structured intelligence. Set up your Polaris7 workspace to monitor relevant companies in your executive briefing.
- Verified primary sources
- Automated briefings
- Instant watchlist setup
Key Takeaways & Evidence Grounding
- Anthropic announced that claude -p would be charged separately from subscriptions as API rates starting June 15.
- HammerMei published an open-source project called poor-claude to preserve long-lived Claude interactive sessions without per-request PTY spawning.
- poor-claude uses Claude Code's experimental MCP Channels to inject prompts and a Stop hook to detect response completion and read session transcripts.
- poor-claude implements a persistent daemon (one process per session), per-session MCP configs, transcript offset tracking, and auto-accept of startup prompts.
- A bootstrap script is available at https://raw.githubusercontent.com/HammerMei/poor-claude/main/scripts/bootstrap.sh and the CLI command is shown as claude-no-p.
Connected Companies & Entities
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Anthropic Claude Code: Five Practical LLM Workflows
A solo founder describes five Claude Code workflows that proved useful in day-to-day development: using git worktrees to run parallel Claude sessions, delegating research to subagents to preserve session memory, enabling plan mode to review changes before edits, using resume/PR linking for continuity across sessions, and avoiding headless automation without checking billing. The post warns that Anthropic split Agent SDK billing from subscription on 2026-06-15 so headless CLI runs (e.g., `claude -p`) now bill against the SDK, not Pro/Max seats. The author links Anthropic docs and notes Anthropic shipped "dynamic workflows" in research preview on 2026-05-28, describing it as the next step beyond subagents.
Anthropic Claude API: Models, Features, and Best Practices
This technical guide explains how to build with Anthropic's Claude API, covering setup, multi-turn chats, streaming, tool use, vision (image) inputs, error handling, and cost-saving techniques. It describes Claude's design priorities—safety plus capability—highlighting a system-prompt hierarchy where operator/system instructions have higher authority than user messages, Constitutional AI training, and very large context windows (200K tokens). The post compares Claude model variants (claude-3-5-sonnet, claude-3-5-haiku, claude-3-opus) including context, speed and per‑token pricing, and details prompt caching (ephemeral cache with ~5 minute TTL), tool-calling patterns, supported image formats, and production best practices for retries and rate-limit handling.
Handling Claude API Rate Limits Without Losing Messages
A developer post describes engineering patterns used in SimplyLouie (a $2/month Claude wrapper with ~100 concurrent users) to prevent user message loss when Anthropic's Claude API returns errors or drops streams. The author catalogs common error codes (529 overloaded, 429 rate-limited, 500 server error, timeouts) and shares concrete patterns and code: persist user messages to the database before sending, use exponential backoff retries for temporary 529/500 errors (up to three attempts), implement reconnect/fallback logic for streaming partial responses, and expose per-user rate-limit state to clients. In production this approach yields about a 2% 529 rate and under 0.1% user-visible failures.
WATCHLIST & BRIEFINGS
Receive future signals for Anthropic & competitors in your briefing
Stay ahead of material M&A deals, leadership changes, account wins, and product rollouts. Polaris7 connects primary filings, company newsrooms, and trade reporting directly into your executive briefing.
- Regular primary-source checks
- Structured Watchlist briefings
- Preserves current context
Market Signal Monitoring
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
Monitor Anthropic
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
