[BUG] Remote trigger completed runs show no logs/transcript in web UI

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?

Remote trigger runs show a green checkmark in the "Runs" section of the scheduled tasks web UI, but clicking on them does nothing. There is no way to view the agent's session transcript, logs, stdout/stderr, or any output from the run.

I have 3 remote triggers (created via the RemoteTrigger API). All show green checkmarks on manual runs, but none produced the expected git commits. Without logs, I cannot determine if the agent failed silently, hit a git push error, encountered an API error, or ran successfully but produced no output.

What Should Happen?

Clicking a completed run should open the session transcript or show logs/output, similar to how GitHub Actions display run logs. At minimum, there should be some way to see what the remote agent did during its execution.

Error Messages/Logs

No logs available. The UI shows:

Runs
✓ Today at 1:04 AM  MANUAL
✓ Today at 12:47 AM MANUAL  
✓ Today at 12:28 AM MANUAL

Clicking any of these does nothing. No expandable section, no link to a transcript, no error output.

Steps to Reproduce

1. Create a remote trigger via the API:

``
RemoteTrigger action: create, with a cron expression, repo source, and prompt
``

1. Fire the trigger manually via RemoteTrigger action: run or the "Run now" button in the web UI
2. Wait for the run to complete (green checkmark appears)
3. Go to the scheduled tasks page in the claude.ai web UI
4. Click on the completed run entry
5. Nothing happens - no logs, no transcript, no output visible

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Claude Code Version

2.1.90 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

The green checkmark is misleading because it implies success, but the agent may have failed to complete its task (no git commits were produced despite 3 "successful" runs). Without any observability into what the remote agent did, debugging remote triggers requires running the same workflow locally to identify issues, which defeats the purpose of remote triggers.

Screenshot of the runs section with no expandable logs:
The runs list shows timestamp + MANUAL tag but no clickable detail view.

<img width="867" height="794" alt="Image" src="https://github.com/user-attachments/assets/3e727efe-9e78-471a-8821-c12a096a7d98" />