RemoteTrigger tool returns 401 despite successful OAuth login

Bug Description

The RemoteTrigger tool consistently returns HTTP 401 authentication errors, even after a successful claude auth login via OAuth.

Steps to Reproduce

1. Run claude auth login — browser opens, login succeeds, CLI confirms "Login successful"
2. Verify with claude auth status:

``json
{"loggedIn": true, "authMethod": "oauth_token", "apiProvider": "firstParty"}
``

1. Use /schedule to create a remote trigger
2. The RemoteTrigger tool call returns:

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

Expected Behavior

RemoteTrigger should authenticate using the OAuth token from claude auth login and successfully create/list triggers.

Actual Behavior

Every RemoteTrigger call (create, list) returns 401. This persists:

• After restarting Claude Code
• Across different repositories
• Across multiple sessions

Environment

• OS: Windows 10 Pro 10.0.19045
• Auth method: oauth_token (firstParty)
• Claude Code version: Latest as of 2026-03-28
• Claude GitHub App: Installed on the target repository

Additional Context

This has been reproduced across multiple repos, not just one. The OAuth token appears valid (auth status confirms it) but the RemoteTrigger API endpoint does not accept it.