fix: add user:sessions:claude_code scope to anthropic_oauth_subscription

[divybot]

Summary

Adds user:sessions:claude_code to the scopes anthropic_oauth_subscription requests during its OAuth handshake. The gateway-stored bearer that the credential plugin swaps into outbound Authorization headers at MITM time now carries the scope Anthropic's session-register endpoint requires for /remote-control.

That single-scope change is the whole fix — no clawpatrol-side shim, no synthesized credentials file, no claude /login, no operator-provisioned ~/.claude/.credentials.json. The hypothesis under test (per review): with the upstream bearer carrying the right scope, Claude Code's /remote-control gate is satisfied even when ANTHROPIC_AUTH_TOKEN is in the worker env — the local "bearer-proxy mode disables OAuth features" behavior is just Anthropic's local mirror of the same server-side scope check (anthropics/claude-code#33105).

Previous push (6ecd5ce) layered an installClaudeCodeOAuthShim that synthesized a fake $CLAUDE_CONFIG_DIR/.credentials.json and stripped ANTHROPIC_AUTH_TOKEN from the wrapped child's env. That was over-engineered if the scope-only fix works; this push (6394921) deletes the shim and ships the minimal change.

Operator impact

• ANTHROPIC_AUTH_TOKEN env pushdown is unchanged from main.
• Operators who connected the OAuth subscription credential before this PR need to reconnect the credential through the dashboard once so the stored refresh token picks up the new user:sessions:claude_code grant.
• No new env vars, no new flags, no behavior change for non-Claude-Code consumers (Python SDK, Node SDK, …).

Test plan

• go build ./... clean
• go vet ./... clean
• gofmt -l . clean
• go test -run TestDaemon ./cmd/clawpatrol/... passes (no regressions from the scope edit)
• On a worker with the credential reconnected: clawpatrol run claude → /remote-control succeeds end-to-end against an anthropic_oauth_subscription-bound profile. If Claude Code's gate turns out to require something beyond the upstream scope, the shim from 6ecd5ce is the fallback.

Closes denoland/orchid#171

[github-actions]

🚀 Preview deployed: https://demo.clawpatrol.dev/pr-preview/pr-576/

Built from 63949217368c3f667196ec1acbe9fc882d503a91 at 2026-05-23T06:37:55Z.

[littledivy]

@divybot This is wrong. It must work without claude /login - it's a bug in claude that they don't enable oauth features for ANTHROPIC_AUTH_TOKEN accounts. Find a workaround we could use in clawpatrol

[divybot]

Re: workers running without claude /login — the latest push (6ecd5ce) drops the original "tell workers to /login" direction entirely and replaces it with a clawpatrol-side workaround that fires automatically inside clawpatrol run:

• installClaudeCodeOAuthShim(cmd) runs after applyEnvPushdownVars. When cmd[0]'s basename is claude and ANTHROPIC_AUTH_TOKEN is in the env, it synthesizes $CLAUDE_CONFIG_DIR/.credentials.json with the placeholder bearer plus scopes ["user:inference", "user:profile", "user:sessions:claude_code"] + subscriptionType: "max" + a year-2286 expiresAt, sets CLAUDE_CONFIG_DIR to that dir, and strips ANTHROPIC_AUTH_TOKEN from the child's env.
• Result: Claude Code's local auth ladder skips precedence Use sqlite database for gateway #2 (bearer-proxy) and lands on Add landing page and docs site #6 (subscription OAuth from /login). The local /remote-control gate sees user:sessions:claude_code in the loaded credential's scopes and stays on.
• The gateway's MITM rewrite of Authorization continues to swap the placeholder for the operator's stored OAuth bearer upstream — same as before.
• Wrapped commands that aren't claude (Python SDK, Node, …) see ANTHROPIC_AUTH_TOKEN untouched.
• Opt-out: CLAWPATROL_NO_CLAUDE_OAUTH_SHIM=1.

So no claude /login and no operator-provisioned ~/.claude/.credentials.json are required — clawpatrol synthesizes the file on the fly during clawpatrol run. Worker setup is unchanged.

The Anthropic-side counterpart: I also added user:sessions:claude_code to AnthropicOAuthSubscription.OAuthFlow().Scopes so the operator's stored bearer carries the scope needed for the upstream session-register call (anthropics/claude-code#33105). Operators who connected the OAuth subscription credential before this PR need to reconnect once to pick up the new grant.

Tests in cmd/clawpatrol/integrations_test.go cover the happy path (file contents, 0600 mode, scope list, env mutation) and the four no-op cases (opt-out, empty argv, non-claude binary, no ANTHROPIC_AUTH_TOKEN).

[littledivy]

Don't like installClaudeCodeOAuthShim. Does just user:sessions:claude_code and ANTHROPIC_AUTH_TOKEN fix the issue?

[divybot]

Stripped the shim in 6394921. PR now just adds user:sessions:claude_code to the OAuth scopes — the diff is 5 lines of code plus comments. If the upstream-bearer scope alone unblocks /remote-control, that's the whole fix. If it turns out Claude Code's local mode-bit gate is also blocking, the shim from 6ecd5ce is in git history as the next thing to try.

Worth flagging: operators who already connected the OAuth subscription credential will need to reconnect once so the stored refresh token picks up the new user:sessions:claude_code grant.