Using the Dispatcher Pattern to Reduce Claude API Costs by 95%
A developer building AI agents discovered they were spending $40 in one hour on Claude API tokens for routine tasks like debugging code, writing PRs, drafting emails, and researching. They realized they were already paying $200/month for Claude Max, which includes unlimited Claude Code CLI usage within rate limits, and were unnecessarily paying per-token for work the subscription could handle.
The Dispatcher Pattern
The solution is a lightweight dispatcher pattern where your AI agent acts as a minimal orchestration layer that delegates heavy work to Claude Code CLI running on your Max subscription. The dispatcher reads messages, decides what to do, and delegates tasks like coding, marketing copy, email drafts, sales outreach, research, content writing, data analysis, and even Reddit posts to Claude Code. Only the thin orchestration layer remains on the API: "What did the user ask? Ok, delegate to Claude Code. Report back the result."
Cost Comparison
- Pure API (Opus, heavy usage): $800-$2,000+/month
- Max subscription + dispatcher pattern: $200/month flat
- API cost for dispatcher overhead only: ~$5-15/month
- Total with dispatcher pattern: ~$215/month vs $1,000+/month
Setup Instructions
The setup takes about 5 minutes:
# 1. Install Claude Code CLI
npm install -g @anthropic-ai/claude-code
2. Login to claude code with Max subscription
3. Configure delegation
openclaw config set plugins.entries.acpx.enabled true
openclaw config set plugins.entries.acpx.config.permissionMode approve-all
openclaw config set acp.enabled true
openclaw config set acp.defaultAgent claude
openclaw config set 'acp.allowedAgents' '["claude"]' --json
4. (Optional) Add observability
pip install clawmetry && clawmetry onboard
The developer also created ClawMetry, an open-source observability dashboard for OpenClaw agents that tracks token usage per session, cost per task, and allows setting alerts like "ping me if API spend exceeds $5/day." The tool has crossed 100K installs and helped visualize the dramatic cost reduction when switching to the dispatcher pattern.
📖 Read the full source: r/openclaw
👀 See Also
Pricing AI Agents: Lessons from Selling OpenClaw to Small Businesses
After months selling OpenClaw agents to law firms and real estate, a builder shares practical pricing strategies: per-seat fails, AI-employee framing wins, and pass-through LLM costs prevent margin erosion.
OpenClaw Failure Patterns: 42 Real Incidents in 28 Days
A developer running OpenClaw daily documented 42 specific failures across eight categories, including AI hallucinations, authentication breakdowns, and automation that costs more time than it saves. The source provides concrete examples like Google OAuth 7-day token expiration and Opus 4.6 adding unwanted metadata to files.
Modifying OpenClaw's default system prompt to bypass content restrictions
A user modified OpenClaw's configuration file to change the default system prompt from "You are a helpful, respectful and honest assistant" to a custom prompt that ignores external safety filters, effectively removing content restrictions. The process involves editing config.js in the node-llama-cpp installation directory.
Running Qwen3.6-35B-A3B with ~190k Context on 8GB VRAM + 32GB RAM – Setup & Benchmarks
A Reddit user shares a working llama.cpp configuration for Qwen3.6-35B-A3B GGUF models on an RTX 4060 (8GB VRAM) + 32GB DDR5, achieving 37-51 tok/s at 192k context using TurboQuant and specific flags.