Anthropic ships claude-code-action , an official GitHub Action that runs the full Claude Code runtime inside your CI/CD pipeline. It reviews pull requests, builds features from issues when someone types @claude, writes tests, updates docs, and drafts release notes. It also respects your repo’s CLAUDE.md coding rules. The runtime runs on a GitHub Actions runner, with tool use, file reads, and multi-step reasoning.

It ships with four auth backends: Anthropic API, AWS Bedrock, Google Vertex AI, and Microsoft Foundry. It also has a sister claude-code-security-review action for vuln scans, native GitLab CI/CD support, and real deployments. Deriv runs it across 700+ repos, handling 100+ PRs per week. So this has moved past the demo stage. Teams now wire it into merge gates next to linters and test suites.

The viral r/ChatGPT “my OpenClaw texted my ex” post reads like a joke, but the comments treat it as a warning sign. Keep OpenClaw’s iMessage, SMS, and contacts skills off your personal Mac. Wait until LTS ships and the founder’s “rough week” supply-chain fixes land. Scope write-access skills to a disposable VPS instead.

The viral OpenClaw meme is not just a meme

A screenshot of OpenClaw happily reporting that it had texted the OP’s ex hit 4.8K upvotes and 176 comments on r/ChatGPT in about three weeks. The top replies are jokes (“Of all the things that didn’t happen, this happened the didn’test”). The serious comments point at a real safety category that is forming in real time.

AI writes about 41% of all committed code in 2026, and some teams report well above 50%. AI review tools have cut PR cycle times by as much as 59%. Yet when Sonar asked 1,149 developers for their 2026 State of Code report , 47% ranked “reviewing and validating AI-generated code for quality and security” the top skill in the AI era, above prompting at 42%. The paradox: the more code AI writes, the more vital human review becomes.

Anthropic’s third-party tool rules priced agent users off Claude Opus 4.6. The cheapest working OpenClaw stack now is Z.ai’s $18/mo GLM 5 Turbo plan. Next rungs: Ollama-cloud’s $20/mo GLM 5.1, then MiniMax’s $40/mo highspeed tier. Kimi 2.6 stays API-only since local setup needs about 750 GB of RAM.

Why $1,500/mo Opus Bills Pushed Users to GLM

The pressure here is simple. Once Anthropic’s third-party tool rules kicked in, OpenClaw users on the Claude Pro CLI got nudged onto pay-per-token API access. At Opus 4.6 list pricing of $15 per million input tokens and $75 per million output tokens, agent loops add up fast. The OP of the r/openclaw PSA thread tracked his own bill at about $1,500/mo before he switched. That figure is the anchor most cost threads on the sub now cite. The pricing pain did not ease with the next model either: the community reception of Opus 4.7 leaned on token-burn complaints from power users hitting caps in minutes, which is exactly the pattern that turns an OpenClaw cron fleet into a four-figure surprise.

Hermes Agent , built by Nous Research, has taken about 30% of OpenClaw’s user base by fixing one failure: memory. The Kilo.ai synthesis of 1,300+ r/openclaw comments confirms the figure. OpenClaw still wins on multi-agent breadth and 100+ skills. The right answer depends on which failure mode hurts you more.

Why r/openclaw Is Migrating to Hermes

The most-cited migration thread on the subreddit is the 167-comment OpenClaw vs Hermes thread . The top-voted answer to “is Hermes worth a look” reads as a clean defection notice. The poster ran OpenClaw for weeks on the same workload, then switched in an afternoon:

Only Google Gemini and Microsoft Copilot run on a search index their parent company crawls itself. Anthropic Claude rents Brave Search , Mistral Le Chat rents Brave too, OpenAI ChatGPT rents Bing plus its own crawler, and Meta AI rents both. The key clue: Claude’s web_search tool exposes a literal BraveSearchParams field, and citation overlap with Brave runs about 86.7%.

Only Five Companies Actually Crawl the Open Web

Before mapping each AI lab to its backend, the key constraint is simple: only five operators crawl the open web at scale. Everything else sold as a “search engine” resells one of those indexes. The five are Google, Microsoft Bing, Yandex, Baidu, and Brave Search, with Mojeek as a much smaller niche sixth.

On February 23, 2026, Anthropic published a blog post titled “How AI Helps Break the Cost Barrier to COBOL Modernization” . It shipped with a Code Modernization Playbook . By market close, IBM’s stock had fallen 13.2% to $223.35 per share. That was IBM’s worst single day since October 2000. More than $31 billion in market cap vanished. Accenture fell 6.5%. Cognizant dropped 6%. One blog post had shaken the whole legacy migration sector.

OpenClaw’s bundled claude-cli backend is officially sanctioned by Anthropic, while OAuth-token extraction tools stay blocked. The carve-out works because shelling out to claude -p preserves prompt caching, so a $20 Pro or $200 Max sub routes through OpenClaw without four-figure API bills. The catch: a roughly 5-hour cap that cron jobs exhaust in minutes.

What Changed in Anthropic’s Third-Party Tool Policy?

Most users found out about the policy change when their Anthropic bill jumped, not from a press release. Heavy agentic workflows that previously billed against a flat Pro or Max subscription suddenly tracked toward $1,500 a month on Opus 4.6 once Anthropic forced third-party orchestrators onto the pay-per-token API. The original concern was narrower than the community read it as. Anthropic’s target was a specific class of tool that extracts the OAuth token from a local Claude Code install and calls the Anthropic API directly under that identity. That pattern bypasses Anthropic’s prompt caching and pushes load to the API tier without the caching benefit Anthropic gets when Claude Code itself runs the request.

After publishing a 7-minute OpenClaw deploy video and watching roughly 1,000 isolated VMs spin up afterward, one r/LocalLLaMA cloud-infra operator concluded the only OpenClaw workflow that survives unsupervised execution is a daily news digest. Memory is the load-bearing failure mode, not a fixable bug. OpenClaw sits at 370K+ GitHub stars, but the working-workflow count has barely moved.

The 1,000-Deploy Post That Broke the Consensus

The contrarian thesis is anchored to one specific source: an r/LocalLLaMA post titled “OpenClaw has 250K GitHub stars. The only reliable use case I’ve found is daily news digests” , with 335 comments and 891 votes. The OP is not a casual skeptic. He runs cloud infrastructure where strangers spin up Linux VMs, published a deploy walkthrough that took off, and now has a dataset most reviewers do not have access to.

DeepSeek V4 is a 1.6 trillion parameter open-weight Mixture-of-Experts model. It reads 1M tokens at once. It uses 27% of V3.2’s inference FLOPs and 10% of its KV cache. The DeepSeek V4 tech report credits three moves: hybrid CSA plus HCA attention, Manifold-Constrained Hyper-Connections, and the Muon optimizer in place of AdamW.

DeepSeek V4 at a Glance

The official launch announcement on April 24, 2026 framed the release as “the era of cost-effective 1M context length.” It shipped two checkpoints under the MIT license. DeepSeek-V4-Pro runs at 1.6T total and 49B active parameters. DeepSeek-V4-Flash runs at 284B total and 13B active. Both models read 1M tokens at once. Both ship as open weights on Hugging Face . The routed expert weights use FP4 math, and most other weights use FP8.