RemoteTrigger tool returns HTTP 401 despite valid OAuth session

Description

The RemoteTrigger tool (used by the schedule skill) consistently returns HTTP 401 authentication errors, even though the CLI session is fully authenticated via OAuth.

Environment

• Claude Code version: 2.1.101
• Auth method: oauth_token
• API provider: firstParty
• Auth status: loggedIn: true (confirmed via claude auth status)
• Platform: macOS (Darwin 25.4.0)

Steps to Reproduce

1. Authenticate via claude /login (OAuth token method)
2. Confirm auth with claude auth status (shows logged in)
3. Use the schedule skill or call RemoteTrigger with action: "list"
4. Every call returns:

HTTP 401
{"type":"error","error":{"type":"authentication_error","message":"Authentication failed"}}

Expected Behavior

RemoteTrigger should authenticate using the same OAuth token the CLI uses for other API calls.

Actual Behavior

All RemoteTrigger actions (list, create, etc.) fail with 401. Retrying and re-authenticating does not help. Meanwhile, the scheduled tasks UI on claude.ai/code/scheduled works fine with the same account, confirming the feature is enabled.

Workaround

Create scheduled triggers manually via the claude.ai web UI at https://claude.ai/code/scheduled.

Additional Context

• Multiple retry attempts across the session all returned the same 401
• The RemoteTrigger tool description states "the OAuth token is added automatically in-process and never exposed," suggesting it should use the existing session token
• This may indicate the RemoteTrigger tool requires a different OAuth scope than what the standard CLI login provides