Anthropic's upcoming billing split on June 15 is forcing developers to get creative. A new open-source project called "poor-claude" offers a workaround that keeps Claude Code running under subscription pricing instead of the more expensive API model that will replace claude -p after the deadline.

The Billing Change That's Stirring Up CI/CD Pipelines

Starting June 15, Anthropic is separating how it charges for different Claude Code modes. The prompt-only -p flag, commonly used in automated scripts and continuous integration workflows, will transition to API-based billing. Interactive mode—which requires an active subscription—will remain on the subscription plan. For teams running hundreds of daily tasks through CI/CD pipelines, this shift could mean unpredictable costs that don't fit tight operational budgets. The core issue is pricing predictability. Subscription plans offer consistent monthly rates, while API calls scale with usage in ways that can surprise developers who assumed their workloads would stay flat. A script that processes 50 pull requests per day might have seemed affordable at a fixed rate but becomes a variable expense under token-based billing.

How the Stopgap Works

The solution is deceptively simple: wrap Claude Code's interactive mode with a Python script that tricks it into treating one-shot tasks as subscription sessions. The claude_task.py script accepts a prompt, spins up an interactive Claude process with --permission-mode bypassPermissions, and waits for the response written to a temporary file before killing the parent process. The implementation uses standard Unix signals and process groups to manage timeouts gracefully. If Claude doesn't respond within the configurable deadline (defaulting to 120 seconds), it retries twice before giving up. Response output gets piped through /tmp/claude-resp-{uuid}.txt files, keeping things stateless for parallel execution across build agents.

Why This Matters for DevOps Teams

The script's design philosophy prioritizes CI/CD compatibility over feature richness—no daemon required, no MCP server complexity, just a single Python file that drops into any environment with Claude Code installed. For teams already stretched thin managing AI tool budgets, this kind of duct-tape solution buys time while they evaluate alternatives or wait for Anthropic to release official pricing tiers for high-volume batch processing.

Key Takeaways

  • June 15 marks the billing split between claude -p (API) and interactive mode (subscription)
  • The poor-claude project uses Python subprocess calls with timeout handling as a stopgap measure
  • No MCP server or daemon required—ideal for ephemeral CI/CD containers

The Bottom Line

This is exactly the kind of scrappy workaround that gets built when companies change pricing without considering how their tools are actually used in production. Anthropic will likely address this eventually, but until then, HammerMei's script fills a real gap for teams who can't justify API rates for repetitive automation tasks.