chore(sync): mirror docs from openclaw/openclaw@84fb62170a
This commit is contained in:
openclaw-docs-sync[bot]
parent
cf2fd398b4
commit
f48ec58528
@ -1,5 +1,5 @@
|
||||
{
|
||||
"repository": "openclaw/openclaw",
|
||||
"sha": "4a85810091659927ec52b787db9d84c47866c950",
|
||||
"syncedAt": "2026-04-05T08:56:33.907Z"
|
||||
"sha": "84fb62170a56b18907891b83861092e4933366d4",
|
||||
"syncedAt": "2026-04-05T09:07:10.945Z"
|
||||
}
|
||||
|
||||
@ -1479,12 +1479,14 @@ Tip: the owner-only `gateway` runtime tool still refuses to rewrite `tools.exec.
|
||||
|
||||
See [/concepts/models](/concepts/models) for fallback behavior and scanning strategy.
|
||||
|
||||
Billing note: Anthropic's public Claude Code docs still include direct Claude
|
||||
Code terminal usage in Claude plan limits. Separately, Anthropic notified
|
||||
OpenClaw users on **April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that the
|
||||
**OpenClaw** Claude-login path counts as third-party harness usage and
|
||||
requires **Extra Usage** billed separately from the subscription. For
|
||||
production, prefer an Anthropic API key or another supported
|
||||
Billing note: We believe Claude Code CLI fallback is likely allowed for local,
|
||||
user-managed automation based on Anthropic's public CLI docs. That said,
|
||||
Anthropic's third-party harness policy creates enough ambiguity around
|
||||
subscription-backed use in external products that we do not recommend it for
|
||||
production. Anthropic also notified OpenClaw users on **April 4, 2026 at
|
||||
12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path counts as
|
||||
third-party harness usage and requires **Extra Usage** billed separately from
|
||||
the subscription. For production, prefer an Anthropic API key or another supported
|
||||
subscription-style provider such as OpenAI Codex, Alibaba Cloud Model Studio
|
||||
Coding Plan, MiniMax Coding Plan, or Z.AI / GLM Coding Plan.
|
||||
|
||||
|
||||
@ -132,5 +132,5 @@ Notes:
|
||||
`--profile-id`.
|
||||
- `paste-token --expires-in <duration>` stores an absolute token expiry from a
|
||||
relative duration such as `365d` or `12h`.
|
||||
- Anthropic billing note: Anthropic's public Claude Code docs still include direct Claude Code terminal usage in Claude plan limits. Separately, Anthropic notified OpenClaw users on **April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path counts as third-party harness usage and requires **Extra Usage** billed separately from the subscription.
|
||||
- Anthropic billing note: We believe Claude Code CLI fallback is likely allowed for local, user-managed automation based on Anthropic's public CLI docs. That said, Anthropic's third-party harness policy creates enough ambiguity around subscription-backed use in external products that we do not recommend it for production. Anthropic also notified OpenClaw users on **April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path counts as third-party harness usage and requires **Extra Usage** billed separately from the subscription.
|
||||
- Anthropic `setup-token` / `paste-token` are available again as a legacy/manual OpenClaw path. Use them with the expectation that Anthropic told OpenClaw users this path requires **Extra Usage**.
|
||||
|
||||
@ -581,12 +581,15 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
|
||||
**local-only models** so your data stays on your device. Subscriptions (Claude
|
||||
Pro/Max or OpenAI Codex) are optional ways to authenticate those providers.
|
||||
|
||||
Anthropic's public Claude Code docs still include direct Claude Code terminal
|
||||
use in Claude plan limits. Separately, Anthropic notified OpenClaw users on
|
||||
**April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that the **OpenClaw**
|
||||
Claude-login path counts as third-party harness usage and now requires
|
||||
**Extra Usage** billed separately from the subscription. OpenAI Codex OAuth
|
||||
is explicitly supported for external tools like OpenClaw.
|
||||
We believe Claude Code CLI fallback is likely allowed for local,
|
||||
user-managed automation based on Anthropic's public CLI docs. That said,
|
||||
Anthropic's third-party harness policy creates enough ambiguity around
|
||||
subscription-backed use in external products that we do not recommend it
|
||||
for production. Anthropic also notified OpenClaw users on **April 4, 2026
|
||||
at 12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path
|
||||
counts as third-party harness usage and now requires **Extra Usage**
|
||||
billed separately from the subscription. OpenAI Codex OAuth is explicitly
|
||||
supported for external tools like OpenClaw.
|
||||
|
||||
OpenClaw also supports other hosted subscription-style options including
|
||||
**Qwen Cloud Coding Plan**, **MiniMax Coding Plan**, and
|
||||
@ -603,13 +606,12 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
|
||||
Yes, via a local **Claude CLI** login on the gateway host.
|
||||
|
||||
Claude Pro/Max subscriptions **do not include an API key**, so Claude CLI
|
||||
reuse is the supported subscription-style path in OpenClaw. Anthropic's
|
||||
public Claude Code docs still cover direct Claude Code terminal use under
|
||||
your plan. Separately, Anthropic told OpenClaw users on **April 4, 2026 at
|
||||
12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path
|
||||
requires **Extra Usage** billed separately from the subscription. If you
|
||||
want the clearest and safest supported path for production, use an
|
||||
Anthropic API key.
|
||||
reuse is the local fallback path in OpenClaw. We believe Claude Code CLI
|
||||
fallback is likely allowed for local, user-managed automation based on
|
||||
Anthropic's public CLI docs. That said, Anthropic's third-party harness
|
||||
policy creates enough ambiguity around subscription-backed use in external
|
||||
products that we do not recommend it for production. We recommend
|
||||
Anthropic API keys instead.
|
||||
|
||||
</Accordion>
|
||||
|
||||
@ -618,11 +620,13 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
|
||||
|
||||
Anthropic setup-token is also available again as a legacy/manual OpenClaw path. Anthropic's OpenClaw-specific billing notice still applies there, so use it with the expectation that Anthropic requires **Extra Usage**. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
|
||||
|
||||
Important: Anthropic's public Claude Code docs still cover direct Claude
|
||||
Code terminal use under Claude plans. Separately, Anthropic told OpenClaw
|
||||
users on **April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that the
|
||||
**OpenClaw** Claude-login path requires **Extra Usage** billed separately
|
||||
from the subscription.
|
||||
Important: We believe Claude Code CLI fallback is likely allowed for local,
|
||||
user-managed automation based on Anthropic's public CLI docs. That said,
|
||||
Anthropic's third-party harness policy creates enough ambiguity around
|
||||
subscription-backed use in external products that we do not recommend it
|
||||
for production. Anthropic also told OpenClaw users on **April 4, 2026 at
|
||||
12:00 PM PT / 8:00 PM BST** that the **OpenClaw** Claude-login path
|
||||
requires **Extra Usage** billed separately from the subscription.
|
||||
|
||||
For production or multi-user workloads, Anthropic API key auth is the
|
||||
safer, recommended choice. If you want other subscription-style hosted
|
||||
|
||||
@ -14,27 +14,35 @@ backend. Existing legacy Anthropic token profiles are still honored at runtime
|
||||
if they are already configured.
|
||||
|
||||
<Warning>
|
||||
Anthropic's public Claude Code docs say direct Claude Code usage is included
|
||||
with Claude subscriptions. Separately, Anthropic notified OpenClaw users on
|
||||
**April 4, 2026 at 12:00 PM PT / 8:00 PM BST** that **OpenClaw counts as a
|
||||
third-party harness**. Their stated policy is that OpenClaw-driven Claude-login
|
||||
traffic no longer uses the included Claude subscription pool and instead
|
||||
requires **Extra Usage** (pay-as-you-go, billed separately from the
|
||||
subscription).
|
||||
Anthropic's public Claude Code docs explicitly document non-interactive CLI
|
||||
usage such as `claude -p`. Based on those docs, we believe local,
|
||||
user-managed Claude Code CLI fallback is likely allowed.
|
||||
|
||||
Separately, Anthropic notified OpenClaw users on **April 4, 2026 at 12:00 PM
|
||||
PT / 8:00 PM BST** that **OpenClaw counts as a third-party harness**. Their
|
||||
stated policy is that OpenClaw-driven Claude-login traffic no longer uses the
|
||||
included Claude subscription pool and instead requires **Extra Usage**
|
||||
(pay-as-you-go, billed separately from the subscription).
|
||||
|
||||
That policy distinction is about **OpenClaw-driven Claude CLI reuse**, not
|
||||
about running `claude` directly in your own terminal.
|
||||
about running `claude` directly in your own terminal. That said, Anthropic's
|
||||
third-party harness policy still leaves enough ambiguity around
|
||||
subscription-backed use in external products that we do not recommend this
|
||||
path for production.
|
||||
|
||||
Anthropic's current direct-Claude-Code plan docs:
|
||||
Anthropic's current public docs:
|
||||
|
||||
- [Claude Code CLI reference](https://code.claude.com/docs/en/cli-reference)
|
||||
- [Claude Agent SDK overview](https://platform.claude.com/docs/en/agent-sdk/overview)
|
||||
|
||||
- [Using Claude Code with your Pro or Max plan](https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan)
|
||||
- [Using Claude Code with your Team or Enterprise plan](https://support.anthropic.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan/)
|
||||
|
||||
If you want a clearer billing path, use an Anthropic API key instead. OpenClaw
|
||||
also supports other subscription-style options, including [OpenAI
|
||||
Codex](/providers/openai), [Qwen Cloud Coding
|
||||
Plan](/providers/qwen), [MiniMax Coding Plan](/providers/minimax),
|
||||
and [Z.AI / GLM Coding Plan](/providers/glm).
|
||||
If you want the clearest billing path, use an Anthropic API key instead.
|
||||
OpenClaw also supports other subscription-style options, including [OpenAI
|
||||
Codex](/providers/openai), [Qwen Cloud Coding Plan](/providers/qwen),
|
||||
[MiniMax Coding Plan](/providers/minimax), and [Z.AI / GLM Coding
|
||||
Plan](/providers/glm).
|
||||
</Warning>
|
||||
|
||||
## Option A: Anthropic API key
|
||||
@ -205,14 +213,16 @@ header while keeping the required OAuth betas.
|
||||
## Option B: Claude CLI as the message provider
|
||||
|
||||
**Best for:** a single-user gateway host that already has Claude CLI installed
|
||||
and signed in with a Claude subscription.
|
||||
and signed in, as a local fallback rather than the recommended production path.
|
||||
|
||||
Billing note: Anthropic's public Claude Code docs cover **direct** Claude Code
|
||||
usage under Pro/Max or Team/Enterprise plans. Separately, Anthropic told
|
||||
OpenClaw users that **OpenClaw-driven** Claude CLI usage is treated as
|
||||
third-party harness traffic. As of **April 4, 2026 at 12:00 PM PT / 8:00 PM
|
||||
BST**, Anthropic says this OpenClaw path requires **Extra Usage** instead of
|
||||
the included Claude subscription limits.
|
||||
Billing note: We believe Claude Code CLI fallback is likely allowed for local,
|
||||
user-managed automation based on Anthropic's public CLI docs. That said,
|
||||
Anthropic's third-party harness policy creates enough ambiguity around
|
||||
subscription-backed use in external products that we do not recommend it for
|
||||
production. Anthropic also told OpenClaw users that **OpenClaw-driven** Claude
|
||||
CLI usage is treated as third-party harness traffic and, as of **April 4, 2026
|
||||
at 12:00 PM PT / 8:00 PM BST**, requires **Extra Usage** instead of the
|
||||
included Claude subscription limits.
|
||||
|
||||
This path uses the local `claude` binary for model inference instead of calling
|
||||
the Anthropic API directly. OpenClaw treats it as a **CLI backend provider**
|
||||
@ -345,11 +355,12 @@ More details: [/gateway/cli-backends](/gateway/cli-backends)
|
||||
|
||||
## Notes
|
||||
|
||||
- Anthropic's public Claude Code plan docs still cover direct Claude Code
|
||||
terminal use under Claude subscriptions. Anthropic's separate notice to
|
||||
OpenClaw users says the **OpenClaw** Claude-login path is third-party harness
|
||||
usage and requires **Extra Usage** (pay-as-you-go billed separately from the
|
||||
subscription).
|
||||
- Anthropic's public Claude Code docs still document direct CLI usage such as
|
||||
`claude -p`. We believe local, user-managed fallback is likely allowed, but
|
||||
Anthropic's separate notice to OpenClaw users says the **OpenClaw**
|
||||
Claude-login path is third-party harness usage and requires **Extra Usage**
|
||||
(pay-as-you-go billed separately from the subscription). For production, we
|
||||
recommend Anthropic API keys instead.
|
||||
- Anthropic setup-token is available again in OpenClaw as a legacy/manual path. Anthropic's OpenClaw-specific billing notice still applies, so use it with the expectation that Anthropic requires **Extra Usage** for this path.
|
||||
- Auth details + reuse rules are in [/concepts/oauth](/concepts/oauth).
|
||||
|
||||
|
||||
@ -197,7 +197,8 @@ openclaw onboard --non-interactive \
|
||||
|
||||
Anthropic setup-token is available again as a legacy/manual onboarding path.
|
||||
Use it with the expectation that Anthropic told OpenClaw users the OpenClaw
|
||||
Claude-login path requires **Extra Usage**.
|
||||
Claude-login path requires **Extra Usage**. For production, prefer an
|
||||
Anthropic API key.
|
||||
|
||||
## Add another agent
|
||||
|
||||
|
||||
@ -133,8 +133,8 @@ What you set:
|
||||
Reuses a local Claude CLI login on the gateway host and switches model
|
||||
selection to a canonical `claude-cli/claude-*` ref.
|
||||
|
||||
This is the preferred interactive Anthropic path in `openclaw onboard` and
|
||||
`openclaw configure`.
|
||||
This is an available local fallback path in `openclaw onboard` and
|
||||
`openclaw configure`. For production, prefer an Anthropic API key.
|
||||
|
||||
- macOS: checks Keychain item "Claude Code-credentials"
|
||||
- Linux and Windows: reuses `~/.claude/.credentials.json` if present
|
||||
|
||||
@ -72,7 +72,7 @@ Onboarding starts with **QuickStart** (defaults) vs **Advanced** (full control).
|
||||
For non-interactive runs, `--secret-input-mode ref` stores env-backed refs in auth profiles instead of plaintext API key values.
|
||||
In non-interactive `ref` mode, the provider env var must be set; passing inline key flags without that env var fails fast.
|
||||
In interactive runs, choosing secret reference mode lets you point at either an environment variable or a configured provider ref (`file` or `exec`), with a fast preflight validation before saving.
|
||||
For Anthropic, interactive onboarding/configure prefers **Anthropic Claude CLI** first, then **Anthropic API key**. Anthropic setup-token is also available again as a legacy/manual OpenClaw path, with Anthropic's OpenClaw-specific **Extra Usage** billing expectation.
|
||||
For Anthropic, interactive onboarding/configure offers **Anthropic Claude CLI** as a local fallback and **Anthropic API key** as the recommended production path. Anthropic setup-token is also available again as a legacy/manual OpenClaw path, with Anthropic's OpenClaw-specific **Extra Usage** billing expectation.
|
||||
2. **Workspace** — Location for agent files (default `~/.openclaw/workspace`). Seeds bootstrap files.
|
||||
3. **Gateway** — Port, bind address, auth mode, Tailscale exposure.
|
||||
In interactive token mode, choose default plaintext token storage or opt into SecretRef.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user