RemoteTrigger tool returns "Not authenticated" despite valid claude auth status

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The RemoteTrigger tool consistently returns Not authenticated with a claude.ai account. Run /login and try again. even though claude auth status confirms the session is active.

Steps to reproduce

1. Run /login — login succeeds
2. Run claude auth status — confirms loggedIn: true, authMethod: claude.ai
3. Call RemoteTrigger with action: create and a valid body
4. Tool returns: Not authenticated with a claude.ai account. Run /login and try again.

Expected behavior

RemoteTrigger should use the active session token automatically (as documented: "the OAuth token is added automatically in-process").

Actual behavior

Tool rejects the call with an auth error regardless of login state.

Auth status output
{
"loggedIn": true,
"authMethod": "claude.ai",
"apiProvider": "firstParty",
"apiKeySource": "/login managed key",
"subscriptionType": null
}

Environment

• Platform: macOS (darwin 25.3.0)
• Shell: zsh
• Claude Code model: claude-sonnet-4-6

What Should Happen?

After a successful /login, the RemoteTrigger tool should automatically use the active session's OAuth token to authenticate API calls to claude.ai — no additional steps required. Calling RemoteTrigger
with a valid body should create the trigger and return the new trigger's details.

Error Messages/Logs

Not authenticated with a claude.ai account. Run /login and try again.                                                                                                                                     
                                                                                                                                                                                                            
This error was returned on every RemoteTrigger call despite a confirmed active session. No additional logs or stack traces were surfaced.

Steps to Reproduce

1. Open Claude Code and run /login — browser auth completes, terminal shows "Login successful"
2. Run claude auth status — confirms loggedIn: true, authMethod: claude.ai
3. In a Claude Code session, invoke the RemoteTrigger tool with:

• action: create
• body:

{
"name": "hex-editor",
"description": "Hex dashboard thread creation proxy for Viewer users",
"prompt": "..."
}

1. Tool immediately returns: Not authenticated with a claude.ai account. Run /login and try again.
2. Tried re-running /login and claude --login multiple times — error persists on every RemoteTrigger call

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.84 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

• The RemoteTrigger tool description states: "the OAuth token is added automatically in-process and never exposed" — suggesting this should be transparent to the user, but it appears the token is not

being injected correctly for this session.

• Running ! /login (shell prefix) and /login (slash command) were both attempted — neither resolved the issue.
• claude --login was also attempted with no change in behavior.
• The org is on a team/enterprise account (LightricksLtd) with subscriptionType: null — it's possible the RemoteTrigger API requires a specific subscription tier or org-level permission that isn't

reflected in the auth status output.

• No custom configuration files or MCP overrides that would interfere with auth.
• Issue is fully reproducible across multiple attempts in the same session.