Anthropic and OpenClaw Timeline: The Full Sequence of Events

Wed, 08 Apr 2026 19:48:42 +0800

Background

On April 4, 2026, Anthropic announced that Claude subscriptions would no longer cover third-party tools such as OpenClaw.

The direct user-level impact was that third-party workflows previously relying on the subscription path for Claude access had to move to alternative access methods or switch to other models.

Timeline (January to April 2026)

January 2026

According to public reports, Anthropic asked the project formerly known as Clawdbot to change its name, citing pronunciation similarity to Claude.

During the same period, community feedback began to appear regarding restrictions on third-party access via subscription credentials.

February 2026

The relevant restrictions were written into the terms of service, further clarifying the boundary between subscriptions and third-party automated invocation.

In the same month, OpenClaw released v4.0 and refactored its underlying architecture into a pluggable model backend. In other words, the model was no longer a single hardcoded entry point and could be switched across multiple providers.

March 2026

Anthropic released Claude Dispatch and Computer Use, covering capabilities such as remote task execution and desktop operation.

In subsequent updates, OpenClaw continued building its compatibility layer, unifying differences across model providers in authentication, tool-call formats, and response schemas, thereby reducing migration costs when switching models.

Public reports also noted that OpenClaw and Anthropic communicated in late March, but the overall strategic direction remained unchanged.

April 4, 2026

Anthropic formally executed the subscription coverage cutoff for third-party tools.

This marked the execution phase of policy adjustments that had been underway for several months.

April 5, 2026

OpenClaw released v4.5 with several main actions:

Reprioritizing model entry points in the onboarding flow
Integrating alternative model paths such as GPT-5.4
Continuing adaptation work for task flow and interaction experience

Based on the release timing, OpenClaw’s switchover capability was not built entirely ad hoc, but rested on the multi-model architecture work launched since February.

Two Parallel Directions in the Process

Viewed along the timeline, both parties advanced different priorities during the same period:

Anthropic: tightening subscription boundaries and integrating official product capabilities
OpenClaw: strengthening model replaceability and cross-model compatibility

These two routes are not inherently contradictory, but they do create competition over entry-point ownership and where user workflows accumulate.

Current Status (as of April 2026)

Based on publicly available information, the following can be confirmed:

The subscription coverage cutoff has been executed
OpenClaw has completed its primary model-path transition and continues iterating
Whether users perceive major changes depends on how strongly their workflows rely on any single model

What to Watch Next

Going forward, the more meaningful signals are not from this single event itself, but from three areas:

Whether boundaries between subscription plans and API usage become more explicit
The long-term performance of multi-model agents in stability, cost, and user experience
Whether user workflows settle primarily at the model layer, tool layer, or a hybrid layer between the two

Connect OpenClaw to Local Gemma 4: Complete Setup Guide

Wed, 08 Apr 2026 18:18:00 +0800

This guide shows how to connect OpenClaw to a local Gemma 4 model through Ollama.

If you have not deployed Gemma 4 locally yet, start here:

How to Run Gemma 4 on a Laptop: 5-Minute Local Setup Guide

Step 1: Start the Ollama API Service

Start Ollama first:

`1`	`ollama serve`

Then verify the API quickly with:

curl http://localhost:11434/api/generate -d '{
  "model": "gemma4:12b",
  "prompt": "Hello"
}'

If you get a model response, your local API is ready.

Step 2: Configure OpenClaw to Use Ollama

The OpenClaw config file is usually located at:

`1`	`~/.openclaw/config.yaml`

Edit config.yaml and add a local model entry under models:

models:
  # Your existing model config...

  gemma4-local:
    provider: ollama
    base_url: http://localhost:11434
    model: gemma4:12b
    timeout: 120s

Step 3: Set Default Model (Optional)

If you want Gemma 4 as the default model:

`1`	`default_model: gemma4-local`

Step 4: Restart and Verify OpenClaw

Restart OpenClaw:

`1`	`openclaw restart`

List available models:

`1`	`openclaw models list`

Run a quick chat test:

`1`	`openclaw chat --model gemma4-local "Hello"`

If the chat returns normally, OpenClaw is successfully connected to local Gemma 4.

Common Troubleshooting

connection refused: make sure ollama serve is running.
Model not found: check model name with ollama list (for example gemma4:12b).
Timeout: increase timeout and test a smaller model first.

OpenClaw on KnightLi Blog