[BUG] Scheduled remote triggers lost gh CLI access

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?

Scheduled remote triggers (remote agents) that use gh CLI commands
stopped working around April 1st. The agent reports "Neither GitHub
MCP tools nor the gh CLI are available in this environment" and cannot
list issues, edit labels, or create PRs. The GitHub Integration
connector is connected on both the legacy Settings > Connectors page
and the new Customize > Connectors page. This was working prior to
~April 1st — the agent was previously able to fork the repo and open
PRs via gh. No changes were made to the trigger configuration.Scheduled remote triggers (remote agents) that use gh CLI commands
stopped working around April 1st. The agent reports "Neither GitHub
MCP tools nor the gh CLI are available in this environment" and cannot
list issues, edit labels, or create PRs. The GitHub Integration
connector is connected on both the legacy Settings > Connectors page
and the new Customize > Connectors page. This was working prior to
~April 1st — the agent was previously able to fork the repo and open
PRs via gh. No changes were made to the trigger configuration.

What Should Happen?

Remote trigger sandboxes should have gh CLI available and
authenticated via the GitHub Integration connector, as they did
before. The agent should be able to run gh issue list, gh pr create,
gh issue edit, etc.

Error Messages/Logs

No GitHub MCP tools are available. Let me try using the gh CLI        
  directly.                                                             
  Neither GitHub MCP tools nor the gh CLI are available in this         
  environment.                                                          
  No issues to process — the required GitHub tooling (gh CLI or GitHub  
  MCP server) is not available to list issues

Steps to Reproduce

1. Connect GitHub Integration via Customize > Connectors
2. Create a scheduled remote trigger (remote agent) with a prompt

that uses gh CLI commands (e.g., gh issue list --label auto-acee)

1. Configure the trigger with a git source:

https://github.com/<org>/<repo>

1. Run the trigger (manually or on schedule)
2. Agent reports gh CLI is not available and cannot perform any

GitHub API operations (issues, PRs, labels)

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.90

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

This is a remote trigger issue