Scheduled remote agent triggers accept run requests (HTTP 200) but never execute

Bug Description

Scheduled remote agent triggers created via the RemoteTrigger API return HTTP 200 on run requests, and runs appear in the web UI history, but the agent never actually executes any commands. No output is produced — no bash commands run, no files are written, no network requests are made.

Environment

• Claude Code version: Latest (via CLI)
• Environment ID: env_01CgkXinGZXmRVUVNK2ui82m (claude-code-default, anthropic_cloud)
• Model: claude-sonnet-4-6
• Account timezone: America/New_York

Steps to Reproduce

1. Create a minimal trigger with a simple task:

{
  "name": "Test Echo",
  "cron_expression": "0 12 * * *",
  "enabled": false,
  "job_config": {
    "ccr": {
      "environment_id": "env_01CgkXinGZXmRVUVNK2ui82m",
      "session_context": {
        "model": "claude-sonnet-4-6",
        "sources": [],
        "allowed_tools": ["Bash"]
      },
      "events": [{
        "data": {
          "uuid": "e1f2a3b4-c5d6-47e8-f9a0-1b2c3d4e5f60",
          "session_id": "",
          "type": "user",
          "parent_tool_use_id": null,
          "message": {
            "content": "Run this command: echo 'hello from agent' && date",
            "role": "user"
          }
        }
      }]
    }
  }
}

1. Trigger a manual run via API: action: "run" → returns HTTP 200
2. Run appears in web UI history at https://claude.ai/code/scheduled/{trigger_id}
3. Nothing executes. No output, no side effects.

Testing Done

We systematically tested 4 triggers with increasing complexity:

| Trigger | Task | Result |
|---------|------|--------|
| trig_01MTDNDdrDV1j7TvRN4pUwVn | Simple echo + date | No output |
| trig_01K2uV7rhxmuWgAQfc2jBpP9 | curl to Telegram API (simple POST) | No message received |
| trig_014R8rxCU8FsoK21qhARH7DE | Clone private repo + curl Telegram | No message received |
| trig_01BMmAcaHXbRqbygDkj76PAw | Full research agent (web search, write, commit, push) | No commit, no message |

Verification that commands work locally:

• The same Telegram curl command works perfectly from local machine
• The GitHub token authenticates successfully (tested via curl to git-upload-pack)
• All tools (Bash, Read, Write, WebSearch) work in local Claude Code sessions

Additional Notes

• The create API works fine (HTTP 200, trigger is created)
• The get API works fine (returns trigger details)
• The update API works fine (successfully updates config)
• The run API returns HTTP 200 but nothing happens
• Earlier in the session, the run API was returning HTTP 500 errors. After adding a GitHub personal access token to the repo source URL, it started returning 200 — but still no execution.
• The run API initially returned HTTP 500 when the repo was private without a token. After fixing that, it returns 200 but still doesn't execute.
• Runs show in web UI history but don't display success/failure status
• This was tested over ~2 hours on 2026-04-04/05

Expected Behavior

The agent should execute the commands specified in the prompt and produce observable side effects (Telegram messages, git commits, etc.).

Actual Behavior

API returns HTTP 200, run appears in history, but no commands are executed.