Scheduled tasks run without GitHub credentials, so any task that requires gh CLI access (e.g. reading private repos, creating issues, opening PRs) fails with auth errors. The GitHub plugin injects credentials for interactive runs but does not carry them into scheduled task sandbox executions.
Current behavior
GH_TOKEN / GITHUB_TOKEN are not available in the scheduled task environment- No MCP GitHub tool is loaded for scheduled runs
gh CLI commands against private repos fail with authentication errors
Gap
Scheduled tasks are a first-class feature, but they cannot perform any GitHub operations. Supporting non-user-auth (e.g. a GitHub App token or bot-scoped token) for scheduled task runs would unblock a broad class of automated workflows without requiring a user session to be active.
Options
- Inject a GitHub App installation token at scheduled task launch time (preferred — no user session dependency)
- Reuse the last-known user token, but scope it to read-only or short-lived use (fragile, session-coupled)
- Expose a plugin config surface to opt specific scheduled tasks into GitHub auth
Action taken on behalf of David Cramer.
Scheduled tasks run without GitHub credentials, so any task that requires
ghCLI access (e.g. reading private repos, creating issues, opening PRs) fails with auth errors. The GitHub plugin injects credentials for interactive runs but does not carry them into scheduled task sandbox executions.Current behavior
GH_TOKEN/GITHUB_TOKENare not available in the scheduled task environmentghCLI commands against private repos fail with authentication errorsGap
Scheduled tasks are a first-class feature, but they cannot perform any GitHub operations. Supporting non-user-auth (e.g. a GitHub App token or bot-scoped token) for scheduled task runs would unblock a broad class of automated workflows without requiring a user session to be active.
Options
Action taken on behalf of David Cramer.