openclaw - ✅(Solved) Fix [Feature]: Anthropic is still defualt in docs/start/openclaw.md example [1 pull requests, 1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62529Fetched 2026-04-08 03:02:59
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
referenced ×3commented ×1cross-referenced ×1labeled ×1

docs/start/openclaw.md:120 uses anthropic/claude-opus-4-6 in the getting-started config snippet. Same issue as the README — new users get pointed to a hostile provider on first setup. Since we decided to be "model-agnostic" I think this policy decision should be put throughout the repo.

Root Cause

docs/start/openclaw.md:120 uses anthropic/claude-opus-4-6 in the getting-started config snippet. Same issue as the README — new users get pointed to a hostile provider on first setup. Since we decided to be "model-agnostic" I think this policy decision should be put throughout the repo.

Fix Action

Fixed

PR fix notes

PR #62545: docs: replace Anthropic model with provider placeholder (#62529)

Description (problem / solution / changelog)

Summary

Docs hardcoded anthropic/claude-opus-4-6 as the example model, but since our main README now is model agnostic we should change our other docs accordingly.

Why it matters: New users may not realize they can use other providers/models. What changed: Replaced hardcoded model strings with <provider>/<model> placeholder in docs/providers/models.md and docs/start/openclaw.md. What did NOT change: No code, config, or logic changes — docs only.

Change Type Docs

Scope Docs

Linked Issue/PR Closes #62529 Root Cause N/A Regression Test Plan N/A User-visible / Behavior Changes None Diagram N/A Security Impact

New permissions/capabilities? No Secrets/tokens handling changed? No New/changed network calls? No Command/tool execution surface changed? No Data access scope changed? No

Repro + Verification N/A — docs-only change. Verified rendered markdown reads correctly. Evidence

Visual inspection of changed files.

Human Verification

Verified both files render the placeholder correctly. Edge cases: N/A Not verified: N/A

Review Conversations

No prior conversations to resolve.

Compatibility / Migration

Backward compatible? Yes Config/env changes? No Migration needed? No

Risks and Mitigations None

Changed files

  • docs/providers/models.md (modified, +1/-1)
  • docs/start/openclaw.md (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Summary

docs/start/openclaw.md:120 uses anthropic/claude-opus-4-6 in the getting-started config snippet. Same issue as the README — new users get pointed to a hostile provider on first setup. Since we decided to be "model-agnostic" I think this policy decision should be put throughout the repo.

Problem to solve

Replace with a supported provider model.

Proposed solution

Replace with a supported provider model.

Alternatives considered

No response

Impact

Everyone is affected, the impact is minimum (I guess it's more expensive).

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

Replace the anthropic/claude-opus-4-6 model with a supported provider model in the docs/start/openclaw.md file.

Guidance

  • Identify a supported provider model that aligns with the "model-agnostic" policy decision.
  • Update the docs/start/openclaw.md file to use the new supported provider model in the getting-started config snippet.
  • Review other parts of the repository, such as the README, to ensure consistency in using supported provider models.
  • Consider documenting the list of supported provider models to avoid similar issues in the future.

Notes

The impact of this issue is considered minimal, but replacing the unsupported model can help prevent potential problems for new users.

Recommendation

Apply workaround: Replace the unsupported provider model with a supported one to ensure a smooth setup experience for new users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING