Claude Opus 4.7 Is Out — Here's Why OpenClaw Shows "configured,missing" and How to Fix It

Anthropic released Claude Opus 4.7 today. If you tried to switch immediately and ran openclaw models list, you likely saw: anthropic/claude-opus-4-7 — default,configured,missing. Your agent is now broken until you revert. Here's what's happening and the safe upgrade path.

What "configured,missing" Means

When OpenClaw shows a model as configured,missing, it means:

• configured — you've told OpenClaw to use this model
• missing — OpenClaw's internal model resolver doesn't recognize the model ID yet

The dangerous part: OpenClaw accepted the config change without failing hard, which means if you ran openclaw models set anthropic/claude-opus-4-7 and it became your default, your agent is now trying to call a model that doesn't resolve — and failing silently or throwing errors on every turn.

Why This Happened

OpenClaw maintains an internal model catalog that maps provider-qualified model IDs to their capabilities (context window, input types, etc.). When Anthropic releases a new model, OpenClaw's catalog needs to be updated to recognize the new ID. That update typically lands in the next OpenClaw release — not instantly when the model goes live upstream.

GitHub issue #67710 was filed today documenting exactly this. As of OpenClaw 2026.4.10–4.14, anthropic/claude-opus-4-7 is not yet in the catalog. The 4.15 release (currently in beta) may include it; watch the changelog.

Immediate Fix: Revert Your Default Model

If you already switched and your agent is broken, revert immediately:

# Revert to Opus 4.6
openclaw models set anthropic/claude-opus-4-6

# Or Sonnet 4.6 if you want something lighter
openclaw models set anthropic/claude-sonnet-4-6

# Restart gateway
openclaw gateway restart

Confirm the revert worked:

openclaw models list | grep "default"

You should see anthropic/claude-opus-4-6 (or sonnet-4-6) marked as default,configured — no missing.

How to Use Opus 4.7 Once OpenClaw Supports It

When the OpenClaw model catalog update lands (likely 4.15 stable), the correct upgrade path will be:

# 1. Update OpenClaw (once 4.15 stable is out)
npm install -g openclaw@latest

# 2. Verify Opus 4.7 resolves correctly before setting as default
openclaw models list | grep "opus-4-7"
# Should show: text+image, context window, no "missing" flag

# 3. Only then set as default
openclaw models set anthropic/claude-opus-4-7
openclaw gateway restart

Do not skip step 2. Setting a missing model as default silently breaks your entire agent until you revert.

Alternative: Direct API Key with Model Override

If you need Opus 4.7 today and can't wait for the catalog update, you can bypass OpenClaw's internal resolver by using a raw API config with an explicit model string. This is less clean but functional:

// In openclaw.json — experimental, use at own risk
{
  "providers": {
    "anthropic": {
      "apiKey": "sk-ant-...",
      "model": "claude-opus-4-7"  // Anthropic's confirmed API model ID
    }
  }
}

Anthropic's official API model ID is claude-opus-4-7 (confirmed in their docs). This bypasses the capability catalog, which means context window and input-type checks won't be enforced — use cautiously. Also note: Opus 4.7 supports high-resolution images (up to 2576px / 3.75MP), 1M token context, 128k max output, and a new xhigh effort level. High-res images use more tokens than before.

Is Opus 4.7 Worth Switching To?

Early signals suggest yes — it was designed to address the compute-rationing degradation that Opus 4.6 users have been experiencing for weeks. Once OpenClaw properly supports it, upgrading makes sense for most active setups.

See our full Opus 4.7 upgrade guide for what to test before switching and the decision table by setup type.

TL;DR

• Opus 4.7 dropped today — but OpenClaw's model catalog doesn't recognize it yet
• Setting it as default = configured,missing = broken agent
• Revert: openclaw models set anthropic/claude-opus-4-6 && openclaw gateway restart
• Wait for OpenClaw 4.15 stable, then verify models list shows no missing before switching
• Tracking: GitHub issue #67710