Skip to content

Feature Request: One-click Anthropic authentication (OAuth flow) #32515

Open
Open
Feature Request: One-click Anthropic authentication (OAuth flow)#32515
Labels
P2Normal backlog priority with limited blast radius.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.enhancementNew feature or requestimpact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.

Description

@andreygalizin
andreygalizin
opened on Mar 3, 2026

Summary

One-click Anthropic authentication (OAuth flow)

Problem to solve

The current authentication setup requires users to understand the difference between API keys and OAuth tokens, manually obtain them, know where to paste them, and debug .env files and config. This is a DevOps workflow — not a user experience. A new user today can spend over an hour in authentication hell before sending a single message.

Proposed solution

Replace the entire auth setup with a single OAuth flow:

    openclaw onboard opens a browser
    User clicks "Sign in with Anthropic"
    OpenClaw detects account type (Pro subscription or API credits) and configures everything automatically
    Done — no tokens, no keys, no .env files

The token prefix already reveals the type (sk-ant-api03- = API key, sk-ant-oat = OAuth token), so auto-detection is feasible today as a minimum improvement.

Alternatives considered

No response

Impact

You could not avoid the fast and wide positive impact.

Evidence/examples

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.enhancementNew feature or requestimpact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions