[BUG] RemoteTrigger tool returns HTTP 401 despite valid authentication

Resolved 💬 2 comments Opened Apr 13, 2026 by ishraq8 Closed Apr 13, 2026

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?

## Description
The RemoteTrigger tool consistently returns HTTP 401 Authentication Failed
when attempting to create a scheduled trigger via Claude Code CLI, even
though the account has access to claude.ai/code/scheduled.

## Steps to reproduce

  1. Use the schedule skill in Claude Code
  2. Ask Claude to create a remote trigger
  3. Claude calls RemoteTrigger with action: "create"
  4. Returns: HTTP 401

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

What Should Happen?

## Expected behavior
Trigger is created successfully.

Error Messages/Logs

Steps to Reproduce

## Steps to reproduce

  1. Use the schedule skill in Claude Code
  2. Ask Claude to create a remote trigger
  3. Claude calls RemoteTrigger with action: "create"
  4. Returns: HTTP 401

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

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

4.6

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

## Environment

  • Claude Code CLI
  • OS: Windows 11
  • Shell: Anaconda Prompt / PowerShell
  • Model: claude-sonnet-4-6
  • Account has access to claude.ai/code/scheduled

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗