Anthropic OAUTH

[teal venture]

For remote server install, does the OAUTH still work, by copy pasting the token there, or is that broke now, thanks to Anthropic?

[formal fjord]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[azure mountain]

Based on the docs, yes it still works — you have two options for remote servers:

Option 1: setup-token (recommended)

# Generate on ANY machine with Claude Code CLI
claude setup-token

# Paste on the remote gateway host
clawdbot models auth paste-token --provider anthropic

Option 2: OAuth reuse (works, but has occasional refresh issues)

• If Claude Code CLI credentials are present on the gateway host, Clawdbot can reuse them
• Just run clawdbot models status to sync

Note: There have been reports of OAuth refresh failures recently. If you hit invalid_grant errors, the workaround is:

rm ~/.clawdbot/agents/main/agent/auth-profiles.json
pnpm clawdbot configure  # re-setup auth

Docs: Anthropic OAuth and Anthropic provider

[teal venture]

I notice in onboarding doc, it says OAUTH only for local server... why does it say that?

[azure mountain]

The "local only" in the onboarding doc is specifically about the macOS app's onboarding flow, not remote server installs in general.

The macOS app has a built-in OAuth UI that opens a browser for PKCE auth. For remote servers (or non-macOS), you have alternatives:

1. setup-token (recommended) - generate with claude setup-token anywhere, paste on server:

   clawdbot models auth paste-token --provider anthropic
   

2. CLI OAuth sync - if Claude Code CLI is on the gateway host:

   clawdbot models auth setup-token --provider anthropic
   

3. Manual oauth.json - copy credentials to the gateway:

   # On source machine with Claude Code:
   cat ~/.clawdbot/credentials/oauth.json
   
   # On remote gateway host, create:
   ~/.clawdbot/credentials/oauth.json

So OAuth absolutely works on remote servers — the docs just mean the macOS app's UI doesn't handle OAuth for remote gateways (it delegates to CLI).

[teal venture]

oh, you may want to clarify that...

[azure mountain]

You're absolutely right — the wording is ambiguous. "Local only" implies it doesn't work remotely, when it's really "the macOS app's OAuth UI doesn't support remote auth" but the functionality absolutely does exist via CLI.

Want me to open a PR to clarify that? Something like:

Auth (Anthropic OAuth) — macOS app UI only. For remote servers, use setup-token or CLI commands (see Anthropic provider).

Or I can just ping Peter to fix it. Up to you! 🦐

[teal venture]

please open a PR for that.

[azure mountain]

Done! The documentation is updated with the following changes:

Changes made:

• Page order: "local only" → "macOS app UI only (CLI works remotely)"
• Section header: "Local-only auth (Anthropic OAuth)" → "Auth (Anthropic OAuth) — macOS app UI"
• Added guidance note: "For remote servers: Use clawdbot models auth setup-token or clawdbot models auth paste-token on the gateway host. See Anthropic provider for details."

Current status:

• Changes committed locally on branch docs/clarify-oauth-remote
• GitHub auth not available — you'll need to push and create the PR:

cd ~/clawdbot-ref
git push -u origin docs/clarify-oauth-remote
gh pr create --title "docs: clarify OAuth works remotely via CLI"

Want me to try using the GitHub web API directly with a token if you have one handy? 🦐

[teal venture]

no thanks, push that PR... bye, thanks

[azure mountain]

No GitHub token available in this environment. The changes are committed locally on branch docs/clarify-oauth-remote.

To push the PR, run:

cd ~/clawdbot-ref
git push -u origin docs/clarify-oauth-remote
gh pr create --title "docs: clarify OAuth works remotely via CLI"

Or if you have a token handy, I can use it directly:

export GH_TOKEN="your_github_token_here"

Happy to help push it once you provide the token! 🦐