OpenClaw adds direct Claude Code and ClawHub listener routes

• Brad Brok's Reddit launch post points to PinkyBot, an MIT-licensed framework that routes persistent agents through Claude Code instead of OAuth-based OpenClaw auth.
• According to the PinkyBot repo, the stack adds long-term memory, messaging, scheduling, and a web dashboard on top of Claude Code, while the launch post says it also works with third-party providers and Ollama.
• A second builder's marketplace post shows the other integration path, an OpenClaw skill installed from ClawHub that connects local image and video rigs to a listener and starts bidding on jobs.
• That ClawHub route runs into trust and ops friction: the builder's follow-up post says ClawHub flags the skill as suspicious because it calls an external API and runs local scripts, while the official ClawHub docs describe ClawHub as the public registry for OpenClaw skills and plugins.
• The cost story is already biting. one OpenClaw user says Claude API rate limits stop larger builds mid-flow, and in another thread a startup operator says an internal OpenClaw deployment is already costing about $500 a day in tokens.

You can browse the PinkyBot source, skim the official ClawHub commands, and read OpenClaw's own Anthropic provider note, which says Claude subscription auth inside OpenClaw now counts as third-party harness usage and requires Extra Usage. The matching HN thread quotes Anthropic's April 4 email almost verbatim. That makes the timing on a direct Claude Code harness feel less like a side project and more like a fast detour around a blocked road.

The interesting part of PinkyBot's README is not just that it uses Claude Code. It packages Claude Code into a full agent runtime with named agents, long-term memory, messaging connectors, triggers, and a FastAPI dashboard.

The repo lists a few concrete mechanics:

• install via curl -fsSL https://pinkybot.ai/install.sh | bash
• run a local API server with pinky --mode api --port 8888
• keep long-lived Claude Agent SDK sessions per agent
• wake agents on webhooks, URL changes, or file changes
• plug in Telegram, Discord, and Slack

That is a much thicker harness than the Reddit pitch makes obvious. It is effectively an alternate control plane for Claude Code.

The second route is more OpenClaw-native. The marketplace builder says users install a skill from ClawHub, complete onboarding, then let their local setup connect to a listener and receive generation jobs.

The job flow in that post and its comments is simple:

1. buyers submit image or video jobs
2. local AI setups generate previews and bid
3. the buyer picks a winner
4. the winning rig gets paid

The snag is distribution. The builder's follow-up says ClawHub flags the skill as suspicious because the skill talks to an external API and can run local scripts, which is exactly the behavior this listener model needs. The official security guide explains why the platform is touchy here: OpenClaw explicitly warns about exposed tools, browser control, allowlists, and filesystem permissions.

OpenClaw's own Anthropic provider page says new setups should use an API key, and says Claude subscription auth inside OpenClaw now requires Extra Usage because Anthropic treats it as third-party harness usage. The HN thread quoting Anthropic's email says enforcement started April 4 with OpenClaw.

That gives PinkyBot's pitch a very specific edge. Its README says it works with your Claude account under Claude Code, and the launch post frames that as a way to skip OAuth jank and run an agent directly on a Claude Max plan.

Meanwhile the rate-limit complaint shows why some users were already looking for a different path even before the policy shift: the user says OpenClaw stalls on larger builds because Claude API rate limits interrupt long flows mid-task.

The most useful detail in the business-use thread is how quickly hobby tooling turns into ops spend. One commenter says a small startup deployment that knows company context, integrates with Jira, GitHub, email, and docs, and stores chat history is running at about $500 per day in tokens.

That same thread maps where OpenClaw is getting pushed first:

• company knowledge agents with internal integrations
• D2C ops for inventory, creative, shipments, and ad analytics
• short-term rental bookkeeping and guest management
• vertical assistants that start domain-specific, then turn into workflow systems

The convergence is pretty clear in those comments. Builders want agent runtimes with memory, tools, and workflow glue. They are now mixing direct Claude Code harnesses and OpenClaw skills to get there, depending on whether the bottleneck is auth, distribution, or token economics.