[BUG] "Run Now" button in scheduled triggers UI ignores custom environment configuration

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 "Run Now" button in the UI of claude.ai/code/scheduled fails to start a run when the trigger is configured with a custom environment. However, firing via the RemoteTrigger API from Claude Code locally (action: "run") works correctly and respects the custom environment. I believe this is because the UI button does not pass the custom environment ID through correctly, but I cannot tell without more debugging information.

What Should Happen?

"Run Now" fires the trigger using the saved custom environment, identical to the API behavior.

Error Messages/Logs

Steps to Reproduce

1. Create a scheduled trigger with a custom environment only able to access a certain whitelist of domains
2. Navigate to https://claude.ai/code/scheduled with a skill that is trying to access a domain on the whitelist, eg: "slack.com"
3. Click "Run Now" on the trigger
4. Observe: run fails to start

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.88

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Note: I used Claude Code to see if an existing issue has already been filed, and we believe this bug is distinct from #40460 (blank sessions) because the run fails to start entirely. Only a pop-up modal "Failed to start run" appears in the top right corner, with no entry underneath nor logs.

Details

• Trigger ID: trig_01Qy18wV8NxWqh1y87J6jxkY
• Custom environment ID: env_01PH73yzNX3JnyTig5RzEtQC
• Default environment ID: env_01SevYC8NNodLDGMQSpMfY4r
• Plan: Claude Max