Remote agent GitHub connector: 're-authorize GitHub in settings' error has no resolution path in settings UI

Summary

When a remote agent (CCR trigger) fails with github_repo_access_denied, the error message says:

"GitHub repository access check failed — re-authorize GitHub in settings"

But there is no path in the Claude.ai settings UI to actually resolve this.

Steps to reproduce

1. Create a remote agent trigger via the schedule skill with a GitHub repo source
2. Attempt to run the trigger via RemoteTrigger API (action: "run")
3. Receive HTTP 400: {"reason": "github_repo_access_denied", "message": "GitHub repository access check failed — re-authorize GitHub in settings"}
4. Navigate to https://claude.ai/settings/connectors
5. Disconnect and reconnect the GitHub connector — error persists
6. Navigate to https://github.com/settings/apps/authorizations — Claude is listed as authorized, but no repo-level controls exist here
7. Navigate to https://github.com/settings/installations — no GitHub Apps installed at all

Root cause

The GitHub connector in Claude.ai settings performs OAuth authorization only (identity). It does not install a GitHub App with repository access permissions. As a result, the remote agent cannot clone the repo even though the connector shows as "connected."

The error message directs users to "re-authorize in settings" but the settings UI has no mechanism to install the GitHub App or grant repo-level access.

Expected behavior

Either:

• The GitHub connector setup flow should include a step to install the GitHub App with repo access (the second OAuth step that grants repo permissions)
• Or the error message should provide a direct link/instructions for how to actually resolve the issue (e.g., install the GitHub App at github.com/apps/claude or similar)

Environment

• Claude Code CLI + claude.ai/settings/connectors
• Remote trigger via schedule skill
• macOS, GitHub account: dmoore8670

Impact

Remote agents using GitHub repo sources are completely non-functional for users who only completed the OAuth connector step without a separate GitHub App installation.